Data augmentation for threat investigation in an enterprise network

ABSTRACT

An endpoint in an enterprise network is instrumented with sensors to detect security-related events occurring on the endpoint. Event data from these sensors is augmented with contextual information about, e.g., a source of each event in order to facilitate improved correlation, analysis, and visualization at a threat management facility for the enterprise network.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 63/042,219 filed on Jun. 22, 2020, the entire content of which ishereby incorporated by reference.

This application is also related to U.S. patent application Ser. No.16/165,274 filed on Oct. 19, 2018, U.S. patent application Ser. No.16/383,315 filed on Apr. 12, 2019, and U.S. patent application Ser. No.16/128,953 filed on Sep. 12, 2018. The entire contents of each of theforegoing applications are hereby incorporated by reference.

FIELD

The present disclosure relates to the use of event streams forrecording, monitoring, and investigation of enterprise security.

BACKGROUND

As enterprise networks become more complex, and security threats becomemore sophisticated, there remains a need for improved techniques formonitoring security events and for identifying and investigatingpotential security threats within the enterprise network.

SUMMARY

An aspect of the present teachings is directed to a filtered data lakefor enterprise security. A data lake for enterprise security is createdfrom an asynchronous stream of security events by deduplicating objectsand creating metadata related to downstream security functions.Deduplication of objects may be efficiently performed with a bloomfilter as objects are ingested into the data lake. The objects may alsobe augmented with metadata arranged in schemas to facilitate monitoringand use within the data lake.

In one aspect, a computer program product disclosed herein may includecomputer executable code embodied in a non-transitory computer readablemedium that, when executing on one or more computing devices, performsthe steps of: storing a data lake containing a first plurality of dataobjects representing security events and a plurality of descriptions forthe first plurality of data objects, where the first plurality of dataobjects include security events from one or more data recorders onendpoints in an enterprise network, and where each of the plurality ofdescriptions is organized according to one or more schemas; receiving asecond plurality of data objects in an asynchronous stream of securityevents from the enterprise network, the asynchronous stream including acombination of batch transfers including groups of security events andstreaming transfers of individual security events; filtering the secondplurality of data objects to remove duplicate data objects alreadyincluded in the first plurality of data objects, where filteringincludes applying at least one bloom filter to identify one of thesecond plurality of data objects that might be in the data lake andperforming a deduplication lookup in the data lake for the one of thesecond plurality of data objects; augmenting each of the secondplurality of data objects with a corresponding description organizedaccording to at least one of the one or more schemas; and storing thesecond plurality of data objects and a corresponding plurality ofdescriptions according to the one or more schemas with the firstplurality of data objects in the data lake.

The computer program product may further include code that performs thesteps of: searching the data lake for one or more security events ofinterest; and, in response to data obtained while searching the datalake, directly querying at least one of the endpoints for additionalinformation.

In one aspect, a method disclosed herein may include storing a data lakecontaining a first plurality of data objects representing securityevents and a plurality of descriptions for the first plurality of dataobjects, each of the plurality of descriptions organized according toone or more schemas; receiving a second plurality of data objects in anasynchronous stream of security events from an enterprise network;filtering the second plurality of data objects to remove duplicate dataobjects already included in the first plurality of data objects;augmenting each of the second plurality of data objects with acorresponding description organized according to at least one of the oneor more schemas; and storing the second plurality of data objects and acorresponding plurality of descriptions according to the one or moreschemas with the first plurality of data objects in the data lake.

The data objects may include security events from one or more endpointsin the enterprise network. At least one of the first plurality of dataobjects and the second plurality of data objects may include securityevents from one or more data recorders on endpoints in the enterprisenetwork. The asynchronous stream may include at least one of a batchtransfer including a group of security events, a streaming transfer ofone or more individual security events, and a connectivity-dependenttransfer. Filtering may include applying a bloom filter to detect afirst group of the second plurality of data objects that are definitelynot in the data lake and a second group of the second plurality of dataobjects that might be in the data lake. The method may further includeperforming a deduplication lookup in the data lake on each of the secondgroup. One of the schemas may include a global schema for all of thedata objects in the data lake. One of the schemas may include adevice-dependent schema selected for one of the data objects accordingto a source of the one of the data objects when received in theasynchronous stream. One or more schemas may be columnar schemas. Themethod may further include programmatically listening to each of thesecond plurality of data objects based on at least one of the one ormore schemas as each of the data objects is stored in the data lake toidentify one or more security events of interest. The method may furtherinclude, in response to identifying a security event of interest,directly querying at least one endpoint in the enterprise network foradditional information. The method may further include searching thedata lake for one or more security events of interest. The method mayfurther include, in response to data obtained while searching the datalake, directly querying at least one endpoint in the enterprise networkfor additional information.

In one aspect, a system disclosed herein may include: a data lakeincluding a data storage medium storing a first plurality of dataobjects representing security events within an enterprise network and aplurality of descriptions for the first plurality of data objects, eachof the plurality of descriptions organized according to one or moreschemas; a stream service configured to receive an asynchronous eventstream of additional data objects representing security events from theenterprise network; and a transformer service configured to process theasynchronous event stream by filtering the additional data objects toremove duplicate one or more data objects already stored in the datalake, thereby providing filtered data objects, to augment each of thefiltered data objects with a corresponding description organizedaccording to one of the one or more schemas, thereby providing augmenteddata objects, and to store the augmented data objects in the data lake.

The asynchronous event stream may include at least one of a batchtransfer including a group of security events, a streaming transfer ofone or more individual security events, and a connectivity-dependenttransfer. Filtering the additional data objects may include applying abloom filter to the asynchronous event stream to detect a first group ofthe additional data objects that are definitely not in the data lake anda second group of the additional data objects that might be in the datalake. The transformer service may be further configured to perform adeduplication lookup in the data lake on each of the second group of theadditional data objects. The system may further include a query engineconfigured to search the data lake for one or more security events ofinterest.

An aspect of the present teachings is directed to live discovery ofenterprise threats based on security query activity. A threat managementsystem provides a collection of queries for investigating securityissues within an enterprise. Useful inferences are drawn about the valueof different queries, and about the security posture of the enterprise,by monitoring contextual activity such as the popularity and context ofquery usage, patterns of end user modification to queries, andpost-query activity.

In one aspect, a computer program product disclosed herein may includecomputer executable code embodied in a non-transitory computer readablemedium that, when executing on one or more computing devices, performsthe steps of: receiving an event stream including security events froman enterprise network at a stream service; storing the event stream in adata lake; storing a plurality of queries for execution against theevent stream, the plurality of queries configured to investigatesecurity issues within the enterprise network based on the event stream;monitoring a usage of the plurality of queries at one or moreadministrative consoles to a threat management facility for theenterprise network; determining a usage history based on the usage ofthe plurality of queries; and initiating an action by the threatmanagement facility based on the usage history. The event stream mayinclude security events from one or more sensors on compute instances inthe enterprise network.

In one aspect, a method disclosed herein may include: storing an eventstream including security events from one or more sensors on computeinstances in an enterprise network; storing a plurality of queries forexecution against the event stream, the plurality of queries configuredto investigate security issues within the enterprise network based onthe event stream; monitoring a usage of the plurality of queries;determining a usage history based on the usage of the plurality ofqueries; and initiating an action by a threat management facility basedon the usage history.

Storing the event stream may include storing the event stream in a datalake. Monitoring the usage may include monitoring queries initiated atone or more administrative consoles for the threat management facility.Monitoring the usage may include monitoring queries for a plurality ofenterprise networks. Monitoring the usage may include monitoring changesto one or more of the plurality of queries. Monitoring the usage mayinclude monitoring post-query remediation activity initiated at one ormore administrative consoles. The usage history may include a popularityof one or more of the plurality of queries. The usage history mayinclude a pattern of changes to one or more of the plurality of queries.The usage history may include a pattern of post-query activitiesinitiated from an administrative console. The usage history may includea context for executing one or more of the plurality of queries.Initiating the action may include identifying a pattern of queriesassociated with a known threat and generating a recommendation for oneor more responsive actions. Initiating the action may include evaluatinga usefulness of one of the plurality of queries based on a pattern ofpost-query activity. Initiating the action may include evaluating ausefulness of one of the plurality of queries based on a pattern ofquery modifications by users.

In one aspect, a system disclosed herein may include: a data lakestoring an event stream including security events from one or moresensors on compute instances in an enterprise network; an administrativeconsole for executing queries against the event stream; a databasestoring a plurality of queries for execution against the event stream atthe administrative console, the plurality of queries configured toinvestigate security issues within the enterprise network based on theevent stream; and a query monitoring agent configured to monitor a usageof the plurality of queries at the administrative console, to determinea usage history based on the usage of the plurality of queries, and toinitiate an action by a threat management facility based on the usagehistory.

The usage history may include a popularity of one or more of theplurality of queries. The usage history may include a pattern of changesto one or more of the plurality of queries. The usage history mayinclude a pattern of post-query activities initiated from theadministrative console. The usage history may include a context forexecuting one or more of the plurality of queries.

An aspect of the present teachings is directed to data augmentation forthreat investigation in an enterprise network. An endpoint in anenterprise network is instrumented with sensors to detectsecurity-related events occurring on the endpoint. Event data from thesesensors is augmented with contextual information about, e.g., a sourceof each event in order to facilitate improved correlation, analysis, andvisualization at a threat management facility for the enterprisenetwork.

In one aspect, a computer program product disclosed herein may includecomputer executable code embodied in a non-transitory computer readablemedium that, when executing on one or more computing devices, performsthe steps of: receiving event data from a sensor on an endpoint, theevent data responsive to an event on the endpoint; generating a sourceidentifier that identifies a source of the event in a context of thesensor, the source identifier including a medium access control addressassociated with the source, an internet protocol address associated withthe source, and a process executing on the endpoint that is associatedwith the source; creating a modified event record that includes theevent data and the source identifier; storing the modified event recordin a data recorder on the endpoint; and transmitting the modified eventrecord to a threat management facility.

The computer program product may further include code that performs thestep of storing a plurality of modified event records in the datarecorder. The computer program product may further include code thatperforms the step of responding to a query from a resource external tothe endpoint for data stored in the data recorder. The computer programproduct may further include code that, when executing on the threatmanagement facility, performs the step of providing a user interface fornavigating a chain of events based on relationships among a plurality ofsource identifiers in a plurality of modified event records received atthe threat management facility. The computer program product may furtherinclude code that, when executing on the threat management facility,performs the step of processing a stream of modified event records toevaluate security threats to an enterprise network. The computer programproduct may further include code that performs the step of processing astream of modified event records at the threat management facility toevaluate a security state of the endpoint.

In one aspect, a method disclosed herein may include: instrumenting anendpoint with a sensor and a local security agent, the sensor configuredto generate an event record in response to an event, and the localsecurity agent configured to locally receive the event record from thesensor; appending a source identifier to the event record thatidentifies a source of the event in a context of the sensor, the sourceidentifier including a physical address associated with the source, anetwork address associated with the source, and at least one temporaladdress assigned by the endpoint to the source of the event, therebyproviding a modified event record including the event record and thesource identifier; and transmitting the modified event record to athreat management facility.

The method may further include determining a relationship of themodified event record with one or more other modified event recordsstored at the threat management facility based on the source identifier.The method may further include determining a relationship of the sourceidentifier with one or more other source identifiers based on aplurality of modified event records received at the threat managementfacility. The method may further include creating a graph that causallyassociates two or more events based on a plurality of source identifiersin a plurality of modified event records received at the threatmanagement facility. The method may further include providing a userinterface for navigating a chain of events based on relationships amonga plurality of source identifiers in a plurality of modified eventrecords received at the threat management facility. The method mayfurther include storing a plurality of modified event records on a datarecorder for the endpoint, the data recorder configured to respond toqueries for event data from the threat management facility. The physicaladdress may include a medium access control address and the networkaddress includes an internet protocol address. The method may furtherinclude determining the context of the sensor by inspecting one or morenetwork resources associated with the endpoint. The temporal address mayinclude an identifier for at least one of a user of the endpoint, adevice associated with the endpoint, a path associated with a computingobject on the endpoint, a process executing on the endpoint, and anapplication on the endpoint. The method may further include processing astream of modified event records at the threat management facility toevaluate security threats to an enterprise network. The method mayfurther include processing a stream of modified event records at thethreat management facility to evaluate a security state of the endpoint.The method may further include processing a stream of modified eventrecords at the threat management facility to deduplicate one or moreevent records base on a reconciliation of source identifiers.

In one aspect, a system disclosed herein may include a local securityagent executing on an endpoint, the local security agent configured to:receive data characterizing an event from a sensor on the endpoint;generate an event record in response to the event; determine a contextof the sensor including a physical address associated with a source ofthe event and a temporal address assigned by the endpoint to the sourceof the event; append a source identifier to the event record thatidentifies the source of the event including the context of the sensor,thereby providing a modified event record including the event record andthe source identifier; and transmit the modified event record to aremote resource.

The system may further include a threat management facility configuredto receive a stream of modified event records from a plurality ofendpoints in an enterprise network that includes the endpoint, and toevaluate security threats to the enterprise network based on the streamof modified event records.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, features, and advantages of thedevices, systems, and methods described herein will be apparent from thefollowing description of particular embodiments thereof, as illustratedin the accompanying drawings. The drawings are not necessarily to scale,emphasis instead being placed upon illustrating the principles of thedevices, systems, and methods described herein.

FIG. 1 depicts a block diagram of a threat management system.

FIG. 2 depicts a block diagram of a threat management system.

FIG. 3 shows a system for enterprise network threat detection.

FIG. 4 illustrates a threat management system.

FIG. 5 illustrates an event graph stored by a data recorder.

FIG. 6 depicts a Sensors, Events, Analytics, and Response (SEAR)environment.

FIG. 7 depicts centralized event collection.

FIG. 8 shows a flow chart of a method for computer augmented threatevaluation.

FIG. 9 shows a user interface for managing intermediate threats in anenterprise network.

FIG. 10 shows a user interface for managing intermediate threats in anenterprise network.

FIG. 11 shows a system for event monitoring and response.

FIG. 12 shows a flow chart of a method for dynamic filtering of endpointevent streams.

FIG. 13 shows a flow chart of a method for forensic query of local eventstreams in an enterprise network.

FIG. 14 shows a platform for managing data related to threat management.

FIG. 15 shows a method for creating a data lake for use in enterprisesecurity.

FIG. 16 shows a method for discovery of enterprise threats based onsecurity query activity.

FIG. 17 shows a method for augmenting data for use in threatinvestigation.

DESCRIPTION

Embodiments will now be described with reference to the accompanyingfigures. The foregoing may, however, be embodied in many different formsand should not be construed as limited to the illustrated embodimentsset forth herein.

All documents mentioned herein are hereby incorporated by reference intheir entirety. References to items in the singular should be understoodto include items in the plural, and vice versa, unless explicitly statedotherwise or clear from the text. Grammatical conjunctions are intendedto express any and all disjunctive and conjunctive combinations ofconjoined clauses, sentences, words, and the like, unless otherwisestated or clear from the context. Thus, the term “or” should generallybe understood to mean “and/or” and so forth.

Recitation of ranges of values herein are not intended to be limiting,referring instead individually to any and all values falling within therange, unless otherwise indicated herein, and each separate value withinsuch a range is incorporated into the specification as if it wereindividually recited herein. The words “about,” “approximately” or thelike, when accompanying a numerical value, are to be construed asindicating a deviation as would be appreciated by one of ordinary skillin the art to operate satisfactorily for an intended purpose. Similarly,words of approximation such as “approximately” or “substantially” whenused in reference to physical characteristics, should be understood tocontemplate a range of deviations that would be appreciated by one ofordinary skill in the art to operate satisfactorily for a correspondinguse, function, purpose, or the like. Ranges of values and/or numericvalues are provided herein as examples only, and do not constitute alimitation on the scope of the described embodiments. Where ranges ofvalues are provided, they are also intended to include each value withinthe range as if set forth individually, unless expressly stated to thecontrary. The use of any and all examples, or exemplary language(“e.g.,” “such as,” or the like) provided herein, is intended merely tobetter illuminate the embodiments and does not pose a limitation on thescope of the embodiments. No language in the specification should beconstrued as indicating any unclaimed element as essential to thepractice of the embodiments.

In the following description, it is understood that terms such as“first,” “second,” “top,” “bottom,” “up,” “down,” and the like, arewords of convenience and are not to be construed as limiting terms.

It should also be understood that endpoints, devices, compute instances,or the like that are referred to as “within” an enterprise network mayalso be “associated with” the enterprise network, e.g., where suchassets are outside an enterprise gateway but nonetheless managed by orin communication with a threat management facility or other centralizedsecurity platform for the enterprise network. Thus, any descriptionreferring to an asset within the enterprise network should be understoodto contemplate a similar asset associated with the enterprise networkregardless of location in a network environment unless a differentmeaning is explicitly provided or otherwise clear from the context.

As described herein, a threat management system may use a Sensor,Events, Analytics, and Response (SEAR) approach to protect enterprisesagainst cybersecurity threats.

FIG. 1 depicts a block diagram of a threat management system 101providing protection against a plurality of threats, such as malware,viruses, spyware, cryptoware, adware, Trojans, spam, intrusion, policyabuse, improper configuration, vulnerabilities, improper access,uncontrolled access, and more. A threat management facility 100 maycommunicate with, coordinate, and control operation of securityfunctionality at different control points, layers, and levels within thesystem 101. A number of capabilities may be provided by a threatmanagement facility 100, with an overall goal to intelligently use thebreadth and depth of information that is available about the operationand activity of compute instances and networks as well as a variety ofavailable controls. Another overall goal is to provide protection neededby an organization that is dynamic and able to adapt to changes incompute instances and new threats. In embodiments, the threat managementfacility 100 may provide protection from a variety of threats to avariety of compute instances in a variety of locations and networkconfigurations.

Just as one example, users of the threat management facility 100 maydefine and enforce policies that control access to and use of computeinstances, networks and data. Administrators may update policies such asby designating authorized users and conditions for use and access. Thethreat management facility 100 may update and enforce those policies atvarious levels of control that are available, such as by directingcompute instances to control the network traffic that is allowed totraverse firewalls and wireless access points, applications and dataavailable from servers, applications and data permitted to be accessedby endpoints, and network resources and data permitted to be run andused by endpoints. The threat management facility 100 may provide manydifferent services, and policy management may be offered as one of theservices.

Turning to a description of certain capabilities and components of thethreat management system 101, an exemplary enterprise facility 102 maybe or may include any networked computer-based infrastructure. Forexample, the enterprise facility 102 may be corporate, commercial,organizational, educational, governmental, or the like. As home networksget more complicated, and include more compute instances at home and inthe cloud, an enterprise facility 102 may also or instead include apersonal network such as a home or a group of homes. The enterprisefacility's 102 computer network may be distributed amongst a pluralityof physical premises such as buildings on a campus, and located in oneor in a plurality of geographical locations. The configuration of theenterprise facility as shown is merely exemplary, and it will beunderstood that there may be any number of compute instances, less ormore of each type of compute instances, and other types of computeinstances. As shown, the exemplary enterprise facility includes afirewall 10, a wireless access point 11, an endpoint 12, a server 14, amobile device 16, an appliance or TOT device 18, a cloud computinginstance 19, and a server 20. Again, the compute instances 10-20depicted are exemplary, and there may be any number or types of computeinstances 10-20 in a given enterprise facility. For example, in additionto the elements depicted in the enterprise facility 102, there may beone or more gateways, bridges, wired networks, wireless networks,virtual private networks, other compute instances, and so on.

The threat management facility 100 may include certain facilities, suchas a policy management facility 112, security management facility 122,update facility 120, definitions facility 114, network access rulesfacility 124, remedial action facility 128, detection techniquesfacility 130, application protection facility 150, asset classificationfacility 160, entity model facility 162, event collection facility 164,event logging facility 166, analytics facility 168, dynamic policiesfacility 170, identity management facility 172, and marketplacemanagement facility 174, as well as other facilities. For example, theremay be a testing facility, a threat research facility, and otherfacilities. It should be understood that the threat management facility100 may be implemented in whole or in part on a number of differentcompute instances, with some parts of the threat management facility ondifferent compute instances in different locations. For example, some orall of one or more of the various facilities 100, 112-174 may beprovided as part of a security agent S that is included in softwarerunning on a compute instance 10-26 within the enterprise facility. Someor all of one or more of the facilities 100, 112-174 may be provided onthe same physical hardware or logical resource as a gateway, such as afirewall 10, or wireless access point 11. Some or all of one or more ofthe facilities may be provided on one or more cloud servers that areoperated by the enterprise or by a security service provider, such asthe cloud computing instance 109.

In embodiments, a marketplace provider 199 may make available one ormore additional facilities to the enterprise facility 102 via the threatmanagement facility 100. The marketplace provider may communicate withthe threat management facility 100 via the marketplace interfacefacility 174 to provide additional functionality or capabilities to thethreat management facility 100 and compute instances 10-26. Asnon-limiting examples, the marketplace provider 199 may be a third-partyinformation provider, such as a physical security event provider; themarketplace provider 199 may be a system provider, such as a humanresources system provider or a fraud detection system provider; themarketplace provider may be a specialized analytics provider; and so on.The marketplace provider 199, with appropriate permissions andauthorization, may receive and send events, observations, inferences,controls, convictions, policy violations, or other information to thethreat management facility. For example, the marketplace provider 199may subscribe to and receive certain events, and in response, based onthe received events and other events available to the marketplaceprovider 199, send inferences to the marketplace interface, and in turnto the analytics facility 168, which in turn may be used by the securitymanagement facility 122.

The identity provider 158 may be any remote identity management systemor the like configured to communicate with an identity managementfacility 172, e.g., to confirm identity of a user as well as provide orreceive other information about users that may be useful to protectagainst threats. In general, the identity provider may be any system orentity that creates, maintains, and manages identity information forprincipals while providing authentication services to relying partyapplications, e.g., within a federation or distributed network. Theidentity provider may, for example, offer user authentication as aservice, where other applications, such as web applications, outsourcethe user authentication step to a trusted identity provider.

In embodiments, the identity provider 158 may provide user identityinformation, such as multi-factor authentication, to a SaaS application.Centralized identity providers such as Microsoft Azure, may be used byan enterprise facility instead of maintaining separate identityinformation for each application or group of applications, and as acentralized point for integrating multifactor authentication. Inembodiments, the identity management facility 172 may communicatehygiene, or security risk information, to the identity provider 158. Theidentity management facility 172 may determine a risk score for a userbased on the events, observations, and inferences about that user andthe compute instances associated with the user. If a user is perceivedas risky, the identity management facility 172 can inform the identityprovider 158, and the identity provider 158 may take steps to addressthe potential risk, such as to confirm the identity of the user, confirmthat the user has approved the SaaS application access, remediate theuser's system, or such other steps as may be useful.

In embodiments, threat protection provided by the threat managementfacility 100 may extend beyond the network boundaries of the enterprisefacility 102 to include clients (or client facilities) such as anendpoint 22 outside the enterprise facility 102, a mobile device 26, acloud computing instance 109, or any other devices, services or the likethat use network connectivity not directly associated with or controlledby the enterprise facility 102, such as a mobile network, a public cloudnetwork, or a wireless network at a hotel or coffee shop. While threatsmay come from a variety of sources, such as from network threats,physical proximity threats, secondary location threats, the computeinstances 10-26 may be protected from threats even when a computeinstance 10-26 is not connected to the enterprise facility 102 network,such as when compute instances 22, 26 use a network that is outside ofthe enterprise facility 102 and separated from the enterprise facility102, e.g., by a gateway, a public network, and so forth.

In some implementations, compute instances 10-26 may communicate withcloud applications, such as a SaaS application 156. The SaaS application156 may be an application that is used by but not operated by theenterprise facility 102. Exemplary commercially available SaaSapplications 156 include Salesforce, Amazon Web Services (AWS)applications, Google Apps applications, Microsoft Office 365applications and so on. A given SaaS application 156 may communicatewith an identity provider 158 to verify user identity consistent withthe requirements of the enterprise facility 102. The compute instances10-26 may communicate with an unprotected server (not shown) such as aweb site or a third-party application through an internetwork 154 suchas the Internet or any other public network, private network, orcombination of these.

In embodiments, aspects of the threat management facility 100 may beprovided as a stand-alone solution. In other embodiments, aspects of thethreat management facility 100 may be integrated into a third-partyproduct. An application programming interface (e.g. a source codeinterface) may be provided such that aspects of the threat managementfacility 100 may be integrated into or used by or with otherapplications. For instance, the threat management facility 100 may bestand-alone in that it provides direct threat protection to anenterprise or computer resource, where protection is subscribed todirectly 100. Alternatively, the threat management facility may offerprotection indirectly, through a third-party product, where anenterprise may subscribe to services through the third-party product,and threat protection to the enterprise may be provided by the threatmanagement facility 100 through the third-party product.

The security management facility 122 may provide protection from avariety of threats by providing, as non-limiting examples, endpointsecurity and control, email security and control, web security andcontrol, reputation-based filtering, machine learning classification,control of unauthorized users, control of guest and non-compliantcomputers, and more.

The security management facility 122 may provide malicious codeprotection to a compute instance. The security management facility 122may include functionality to scan applications, files, and data formalicious code, remove or quarantine applications and files, preventcertain actions, perform remedial actions, as well as other securitymeasures. Scanning may use any of a variety of techniques, includingwithout limitation signatures, identities, classifiers, and othersuitable scanning techniques. In embodiments, the scanning may includescanning some or all files on a periodic basis, scanning an applicationwhen the application is executed, scanning data transmitted to or from adevice, scanning in response to predetermined actions or combinations ofactions, and so forth. The scanning of applications, files, and data maybe performed to detect known or unknown malicious code or unwantedapplications. Aspects of the malicious code protection may be provided,for example, in the security agent of an endpoint 12, in a wirelessaccess point 11 or firewall 10, as part of application protection 150provided by the cloud, and so on.

In an embodiment, the security management facility 122 may provide foremail security and control, for example to target spam, viruses,spyware, and phishing, to control email content, and the like. Emailsecurity and control may protect against inbound and outbound threats,protect email infrastructure, prevent data leakage, provide spamfiltering, and more. Aspects of the email security and control may beprovided, for example, in the security agent of an endpoint 12, in awireless access point 11 or firewall 10, as part of applicationprotection 150 provided by the cloud, and so on.

In an embodiment, security management facility 122 may provide for websecurity and control, for example, to detect or block viruses, spyware,malware, unwanted applications, help control web browsing, and the like,which may provide comprehensive web access control enabling safe,productive web browsing. Web security and control may provide Internetuse policies, reporting on suspect compute instances, security andcontent filtering, active monitoring of network traffic, URI filtering,and the like. Aspects of the web security and control may be provided,for example, in the security agent of an endpoint 12, in a wirelessaccess point 11 or firewall 10, as part of application protection 150provided by the cloud, and so on.

In an embodiment, the security management facility 122 may provide fornetwork access control, which generally controls access to and use ofnetwork connections. Network control may stop unauthorized, guest, ornon-compliant systems from accessing networks, and may control networktraffic that is not otherwise controlled at the client level. Inaddition, network access control may control access to virtual privatenetworks (VPN), where VPNs may, for example, include communicationsnetworks tunneled through other networks and establishing logicalconnections acting as virtual networks. In embodiments, a VPN may betreated in the same manner as a physical network. Aspects of networkaccess control may be provided, for example, in the security agent of anendpoint 12, in a wireless access point 11 or firewall 10, as part ofapplication protection 150 provided by the cloud, e.g., from the threatmanagement facility 100 or other network resource(s).

In an embodiment, the security management facility 122 may provide forhost intrusion prevention through behavioral monitoring and/or runtimemonitoring, which may guard against unknown threats by analyzingapplication behavior before or as an application runs. This may includemonitoring code behavior, application programming interface calls madeto libraries or to the operating system, or otherwise monitoringapplication activities. Monitored activities may include, for example,reading and writing to memory, reading and writing to disk, networkcommunication, process interaction, and so on. Behavior and runtimemonitoring may intervene if code is deemed to be acting in a manner thatis suspicious or malicious. Aspects of behavior and runtime monitoringmay be provided, for example, in the security agent of an endpoint 12,in a wireless access point 11 or firewall 10, as part of applicationprotection 150 provided by the cloud, and so on.

In an embodiment, the security management facility 122 may provide forreputation filtering, which may target or identify sources of knownmalware. For instance, reputation filtering may include lists of URIs ofknown sources of malware or known suspicious IP addresses, code authors,code signers, or domains, that when detected may invoke an action by thethreat management facility 100. Based on reputation, potential threatsources may be blocked, quarantined, restricted, monitored, or somecombination of these, before an exchange of data can be made. Aspects ofreputation filtering may be provided, for example, in the security agentof an endpoint 12, in a wireless access point 11 or firewall 10, as partof application protection 150 provided by the cloud, and so on. Inembodiments, some reputation information may be stored on a computeinstance 10-26, and other reputation data available through cloudlookups to an application protection lookup database, such as may beprovided by application protection 150.

In embodiments, information may be sent from the enterprise facility 102to a third party, such as a security vendor, or the like, which may leadto improved performance of the threat management facility 100. Ingeneral, feedback may be useful for any aspect of threat detection. Forexample, the types, times, and number of virus interactions that anenterprise facility 102 experiences may provide useful information forthe preventions of future virus threats. Feedback may also be associatedwith behaviors of individuals within the enterprise, such as beingassociated with most common violations of policy, network access,unauthorized application loading, unauthorized external device use, andthe like. In embodiments, feedback may enable the evaluation orprofiling of client actions that are violations of policy that mayprovide a predictive model for the improvement of enterprise policies.

An update management facility 120 may provide control over when updatesare performed. The updates may be automatically transmitted, manuallytransmitted, or some combination of these. Updates may include software,definitions, reputations or other code or data that may be useful to thevarious facilities. For example, the update facility 120 may managereceiving updates from a provider, distribution of updates to enterprisefacility 102 networks and compute instances, or the like. Inembodiments, updates may be provided to the enterprise facility's 102network, where one or more compute instances on the enterprisefacility's 102 network may distribute updates to other computeinstances.

The threat management facility 100 may include a policy managementfacility 112 that manages rules or policies for the enterprise facility102. Exemplary rules include access permissions associated withnetworks, applications, compute instances, users, content, data, and thelike. The policy management facility 112 may use a database, a textfile, other data store, or a combination to store policies. In anembodiment, a policy database may include a block list, a black list, anallowed list, a white list, and more. As a few non-limiting examples,policies may include a list of enterprise facility 102 external networklocations/applications that may or may not be accessed by computeinstances, a list of types/classifications of network locations orapplications that may or may not be accessed by compute instances, andcontextual rules to evaluate whether the lists apply. For example, theremay be a rule that does not permit access to sporting websites. When awebsite is requested by the client facility, a security managementfacility 122 may access the rules within a policy facility to determineif the requested access is related to a sporting website.

The policy management facility 112 may include access rules and policiesthat are distributed to maintain control of access by the computeinstances 10-26 to network resources. Exemplary policies may be definedfor an enterprise facility, application type, subset of applicationcapabilities, organization hierarchy, compute instance type, user type,network location, time of day, connection type, or any other suitabledefinition. Policies may be maintained through the threat managementfacility 100, in association with a third party, or the like. Forexample, a policy may restrict instant messaging (IM) activity bylimiting such activity to support personnel when communicating withcustomers. More generally, this may allow communication for departmentsas necessary or helpful for department functions, but may otherwisepreserve network bandwidth for other activities by restricting the useof IM to personnel that need access for a specific purpose. In anembodiment, the policy management facility 112 may be a stand-aloneapplication, may be part of the network server facility 142, may be partof the enterprise facility 102 network, may be part of the clientfacility, or any suitable combination of these.

The policy management facility 112 may include dynamic policies that usecontextual or other information to make security decisions. As describedherein, the dynamic policies facility 170 may generate policiesdynamically based on observations and inferences made by the analyticsfacility. The dynamic policies generated by the dynamic policy facility170 may be provided by the policy management facility 112 to thesecurity management facility 122 for enforcement.

In embodiments, the threat management facility 100 may provideconfiguration management as an aspect of the policy management facility112, the security management facility 122, or some combination.Configuration management may define acceptable or requiredconfigurations for the compute instances 10-26, applications, operatingsystems, hardware, or other assets, and manage changes to theseconfigurations. Assessment of a configuration may be made againststandard configuration policies, detection of configuration changes,remediation of improper configurations, application of newconfigurations, and so on. An enterprise facility may have a set ofstandard configuration rules and policies for particular computeinstances which may represent a desired state of the compute instance.For example, on a given compute instance 12, 14, 18, a version of aclient firewall may be required to be running and installed. If therequired version is installed but in a disabled state, the policyviolation may prevent access to data or network resources. A remediationmay be to enable the firewall. In another example, a configurationpolicy may disallow the use of USB disks, and policy management 112 mayrequire a configuration that turns off USB drive access via a registrykey of a compute instance. Aspects of configuration management may beprovided, for example, in the security agent of an endpoint 12, in awireless access point 11 or firewall 10, as part of applicationprotection 150 provided by the cloud, or any combination of these.

In embodiments, the threat management facility 100 may also provide forthe isolation or removal of certain applications that are not desired ormay interfere with the operation of a compute instance 10-26 or thethreat management facility 100, even if such application is not malwareper se. The operation of such products may be considered a configurationviolation. The removal of such products may be initiated automaticallywhenever such products are detected, or access to data and networkresources may be restricted when they are installed and running. In thecase where such applications are services which are provided indirectlythrough a third-party product, the applicable application or processesmay be suspended until action is taken to remove or disable thethird-party product.

The policy management facility 112 may also require update management(e.g., as provided by the update facility 120). Update management forthe security facility 122 and policy management facility 112 may beprovided directly by the threat management facility 100, or, forexample, by a hosted system. In embodiments, the threat managementfacility 100 may also provide for patch management, where a patch may bean update to an operating system, an application, a system tool, or thelike, where one of the reasons for the patch is to reduce vulnerabilityto threats.

In embodiments, the security facility 122 and policy management facility112 may push information to the enterprise facility 102 network and/orthe compute instances 10-26, the enterprise facility 102 network and/orcompute instances 10-26 may pull information from the security facility122 and policy management facility 112, or there may be a combination ofpushing and pulling of information. For example, the enterprise facility102 network and/or compute instances 10-26 may pull update informationfrom the security facility 122 and policy management facility 112 viathe update facility 120, an update request may be based on a timeperiod, by a certain time, by a date, on demand, or the like. In anotherexample, the security facility 122 and policy management facility 112may push the information to the enterprise facility's 102 network and/orcompute instances 10-26 by providing notification that there are updatesavailable for download and/or transmitting the information. In anembodiment, the policy management facility 112 and the security facility122 may work in concert with the update management facility 120 toprovide information to the enterprise facility's 102 network and/orcompute instances 10-26. In various embodiments, policy updates,security updates and other updates may be provided by the same ordifferent modules, which may be the same or separate from a securityagent running on one of the compute instances 10-26.

As threats are identified and characterized, the definition facility 114of the threat management facility 100 may manage definitions used todetect and remediate threats. For example, identity definitions may beused for scanning files, applications, data streams, etc. for thedetermination of malicious code. Identity definitions may includeinstructions and data that can be parsed and acted upon for recognizingfeatures of known or potentially malicious code. Definitions also mayinclude, for example, code or data to be used in a classifier, such as aneural network or other classifier that may be trained using machinelearning. Updated code or data may be used by the classifier to classifythreats. In embodiments, the threat management facility 100 and thecompute instances 10-26 may be provided with new definitionsperiodically to include most recent threats. Updating of definitions maybe managed by the update facility 120, and may be performed upon requestfrom one of the compute instances 10-26, upon a push, or somecombination. Updates may be performed upon a time period, on demand froma device 10-26, upon determination of an important new definition or anumber of definitions, and so on.

A threat research facility (not shown) may provide a continuouslyongoing effort to maintain the threat protection capabilities of thethreat management facility 100 in light of continuous generation of newor evolved forms of malware. Threat research may be provided byresearchers and analysts working on known threats, in the form ofpolicies, definitions, remedial actions, and so on.

The security management facility 122 may scan an outgoing file andverify that the outgoing file is permitted to be transmitted accordingto policies. By checking outgoing files, the security managementfacility 122 may be able discover threats that were not detected on oneof the compute instances 10-26, or policy violation, such transmittal ofinformation that should not be communicated unencrypted.

The threat management facility 100 may control access to the enterprisefacility 102 networks. A network access facility 124 may restrict accessto certain applications, networks, files, printers, servers, databases,and so on. In addition, the network access facility 124 may restrictuser access under certain conditions, such as the user's location, usagehistory, need to know, job position, connection type, time of day,method of authentication, client-system configuration, or the like.Network access policies may be provided by the policy managementfacility 112, and may be developed by the enterprise facility 102, orpre-packaged by a supplier. Network access facility 124 may determine ifa given compute instance 10-22 should be granted access to a requestednetwork location, e.g., inside or outside of the enterprise facility102. Network access facility 124 may determine if a compute instance 22,26 such as a device outside the enterprise facility 102 may access theenterprise facility 102. For example, in some cases, the policies mayrequire that when certain policy violations are detected, certainnetwork access is denied. The network access facility 124 maycommunicate remedial actions that are necessary or helpful to bring adevice back into compliance with policy as described below with respectto the remedial action facility 128. Aspects of the network accessfacility 124 may be provided, for example, in the security agent of theendpoint 12, in a wireless access point 11, in a firewall 10, as part ofapplication protection 150 provided by the cloud, and so on.

In an embodiment, the network access facility 124 may have access topolicies that include one or more of a block list, a black list, anallowed list, a white list, an unacceptable network site database, anacceptable network site database, a network site reputation database, orthe like of network access locations that may or may not be accessed bythe client facility. Additionally, the network access facility 124 mayuse rule evaluation to parse network access requests and apply policies.The network access rule facility 124 may have a generic set of policiesfor all compute instances, such as denying access to certain types ofwebsites, controlling instant messenger accesses, or the like. Ruleevaluation may include regular expression rule evaluation, or other ruleevaluation method(s) for interpreting the network access request andcomparing the interpretation to established rules for network access.Classifiers may be used, such as neural network classifiers or otherclassifiers that may be trained by machine learning.

The threat management facility 100 may include an asset classificationfacility 160. The asset classification facility will discover the assetspresent in the enterprise facility 102. A compute instance such as anyof the compute instances 10-26 described herein may be characterized asa stack of assets. The one level asset is an item of physical hardware.The compute instance may be, or may be implemented on physical hardware,and may have or may not have a hypervisor, or may be an asset managed bya hypervisor. The compute instance may have an operating system (e.g.,Windows, MacOS, Linux, Android, iOS). The compute instance may have oneor more layers of containers. The compute instance may have one or moreapplications, which may be native applications, e.g., for a physicalasset or virtual machine, or running in containers within a computingenvironment on a physical asset or virtual machine, and thoseapplications may link libraries or other code or the like, e.g., for auser interface, cryptography, communications, device drivers,mathematical or analytical functions and so forth. The stack may alsointeract with data. The stack may also or instead interact with users,and so users may be considered assets.

The threat management facility may include entity models 162. The entitymodels may be used, for example, to determine the events that aregenerated by assets. For example, some operating systems may provideuseful information for detecting or identifying events. For examples,operating systems may provide process and usage information thataccessed through an API. As another example, it may be possible toinstrument certain containers to monitor the activity of applicationsrunning on them. As another example, entity models for users may defineroles, groups, permitted activities and other attributes.

The event collection facility 164 may be used to collect events from anyof a wide variety of sensors that may provide relevant events from anasset, such as sensors on any of the compute instances 10-26, theapplication protection facility 150, a cloud computing instance 109 andso on. The events that may be collected may be determined by the entitymodels. There may be a variety of events collected. Events may include,for example, events generated by the enterprise facility 102 or thecompute instances 10-26, such as by monitoring streaming data through agateway such as firewall 10 and wireless access point 11, monitoringactivity of compute instances, monitoring stored files/data on thecompute instances 10-26 such as desktop computers, laptop computers,other mobile computing devices, and cloud computing instances 19, 109.Events may range in granularity. An exemplary event may be communicationof a specific packet over the network. Another exemplary event may beidentification of an application that is communicating over a network.

The event logging facility 166 may be used to store events collected bythe event collection facility 164. The event logging facility 166 maystore collected events so that they can be accessed and analyzed by theanalytics facility 168. Some events may be collected locally, and someevents may be communicated to an event store in a central location orcloud facility. Events may be logged in any suitable format.

Events collected by the event logging facility 166 may be used by theanalytics facility 168 to make inferences and observations about theevents. These observations and inferences may be used as part ofpolicies enforced by the security management facility Observations orinferences about events may also be logged by the event logging facility166.

When a threat or other policy violation is detected by the securitymanagement facility 122, the remedial action facility 128 may be used toremediate the threat. Remedial action may take a variety of forms,non-limiting examples including collecting additional data about thethreat, terminating or modifying an ongoing process or interaction,sending a warning to a user or administrator, downloading a data filewith commands, definitions, instructions, or the like to remediate thethreat, requesting additional information from the requesting device,such as the application that initiated the activity of interest,executing a program or application to remediate against a threat orviolation, increasing telemetry or recording interactions for subsequentevaluation, (continuing to) block requests to a particular networklocation or locations, scanning a requesting application or device,quarantine of a requesting application or the device, isolation of therequesting application or the device, deployment of a sandbox, blockingaccess to resources, e.g., a USB port, or other remedial actions. Moregenerally, the remedial action facility 122 may take any steps or deployany measures suitable for addressing a detection of a threat, potentialthreat, policy violation or other event, code or activity that mightcompromise security of a computing instance 10-26 or the enterprisefacility 102.

FIG. 2 depicts a block diagram of a threat management system 201 such asany of the threat management systems described herein, and including acloud enterprise facility 280. The cloud enterprise facility 280 mayinclude servers 284, 286, and a firewall 282. The servers 284, 286 onthe cloud enterprise facility 280 may run one or more enterpriseapplications and make them available to the enterprise facilities 102compute instances 10-26. It should be understood that there may be anynumber of servers 284, 286 and firewalls 282, as well as other computeinstances in a given cloud enterprise facility 280. It also should beunderstood that a given enterprise facility may use both SaaSapplications 156 and cloud enterprise facilities 280, or, for example, aSaaS application 156 may be deployed on a cloud enterprise facility 280.As such, the configurations in FIG. 1 and FIG. 2 are shown by way ofexamples and not exclusive alternatives.

FIG. 3 shows a system 300 for enterprise network threat detection. Thesystem 300 may use any of the various tools and techniques for threatmanagement contemplated herein. In the system, a number of endpointssuch as the endpoint 302 may log events in a data recorder 304. A localagent on the endpoint 302 such as the security agent 306 may filter thisdata and feeds a filtered data stream to a threat management facility308 such as a central threat management facility or any of the otherthreat management facilities described herein. The threat managementfacility 308 can locally or globally tune filtering by local agentsbased on the current data stream, and can query local event datarecorders for additional information where necessary or helpful inthreat detection or forensic analysis. The threat management facility308 may also or instead store and deploys a number of security toolssuch as a web-based user interface that is supported by machine learningmodels to aid in the identification and assessment of potential threatsby a human user. This may, for example, include machine learninganalysis of new code samples, models to provide human-readable contextfor evaluating potential threats, and any of the other tools ortechniques described herein. More generally, the threat managementfacility 308 may provide any of a variety of threat management tools 316to aid in the detection, evaluation, and remediation of threats orpotential threats.

The threat management facility 308 may perform a range of threatmanagement functions such as any of those described herein. The threatmanagement facility 308 may generally include an application programminginterface 310 to third party services 320, a user interface 312 foraccess to threat management and network administration functions, and anumber of threat detection tools 314.

In general, the application programming interface 310 may supportprogrammatic connections with third party services 320. The applicationprogramming interface 310 may, for example, connect to Active Directoryor other customer information about files, data storage, identities anduser profiles, roles, access privileges and so forth. More generally theapplication programming interface 310 may provide a programmaticinterface for customer or other third party context, information,administration and security tools, and so forth. The applicationprogramming interface 310 may also or instead provide a programmaticinterface for hosted applications, identity provider integration toolsor services, and so forth.

The user interface 312 may include a web site or other graphicalinterface or the like, and may generally provide an interface for userinteraction with the threat management facility 308, e.g., for threatdetection, network administration, audit, configuration and so forth.This user interface 312 may generally facilitate human curation ofintermediate threats as contemplated herein, e.g., by presentingintermediate threats along with other supplemental information, andproviding controls for user to dispose of such intermediate threats asdesired, e.g., by permitting execution or access, by denying executionor access, or by engaging in remedial measures such as sandboxing,quarantining, vaccinating, and so forth.

The threat detection tools 314 may be any of the threat detection tools,algorithms, techniques or the like described herein, or any other toolsor the like useful for detecting threats or potential threats within anenterprise network. This may, for example, include signature basedtools, behavioral tools, machine learning models, and so forth. Ingeneral, the threat detection tools 314 may use event data provided byendpoints within the enterprise network, as well as any other availablecontext such as network activity, heartbeats, and so forth to detectmalicious software or potentially unsafe conditions for a network orendpoints connected to the network. In one aspect, the threat detectiontools 314 may usefully integrate event data from a number of endpoints(including, e.g., network components such as gateways, routers, andfirewalls) for improved threat detection in the context of complex ordistributed threats. The threat detection tools 314 may also or insteadinclude tools for reporting to a separate modeling and analysis platform318, e.g., to support further investigation of security issues, creationor refinement of threat detection models or algorithms, review andanalysis of security breaches, and so forth.

The threat management tools 316 may generally be used to manage orremediate threats to the enterprise network that have been identifiedwith the threat detection tools 314 or otherwise. Threat managementtools 316 may, for example, include tools for sandboxing, quarantining,removing, or otherwise remediating or managing malicious code ormalicious activity, e.g., using any of the techniques described herein.

The endpoint 302 may be any of the endpoints or other compute instancesor the like described herein. This may, for example, include end-usercomputing devices, mobile devices, firewalls, gateways, servers, routersand any other computing devices or instances that might connect to anenterprise network. As described above, the endpoint 302 may generallyinclude a security agent 306 that locally supports threat management onthe endpoint 302, such as by monitoring for malicious activity, managingsecurity components on the endpoint 302, maintaining policy compliance,and communicating with the threat management facility 308 to supportintegrated security protection as contemplated herein. The securityagent 306 may, for example, coordinate instrumentation of the endpoint302 to detect various event types involving various computing objects onthe endpoint 302, and supervise logging of events in a data recorder304. The security agent 306 may also or instead scan computing objectssuch as electronic communications or files, monitor behavior ofcomputing objects such as executables, and so forth. The security agent306 may, for example, apply signature-based or behavioral threatdetection techniques, machine learning models (e.g. models developed bythe modeling and analysis platform), or any other tools or the likesuitable for detecting malware or potential malware on the endpoint 302.

The data recorder 304 may log events occurring on or related to theendpoint. This may, for example, include events associated withcomputing objects on the endpoint 302 such as file manipulations,software installations, and so forth. This may also or instead includeactivities directed from the endpoint 302, such as requests for contentfrom Uniform Resource Locators or other network activity involvingremote resources. The data recorder 304 may record data at any frequencyand any level of granularity consistent with proper operation of theendpoint 302 in an intended or desired manner.

The endpoint 302 may include a filter 322 to manage a flow ofinformation from the data recorder 304 to a remote resource such as thethreat detection tools 314 of the threat management facility 308. Inthis manner, a detailed log of events may be maintained locally on eachendpoint, while network resources can be conserved for reporting of afiltered event stream that contains information believed to be mostrelevant to threat detection. The filter 322 may also or instead beconfigured to report causal information that causally relatescollections of events to one another. In general, the filter 322 may beconfigurable so that, for example, the threat management facility 308can increase or decrease the level of reporting based on a currentsecurity status of the endpoint, a group of endpoints, the enterprisenetwork, and the like. The level of reporting may also or instead bebased on currently available network and computing resources, or anyother appropriate context.

In another aspect, the endpoint 302 may include a query interface 324 sothat remote resources such as the threat management facility 308 canquery the data recorder 304 remotely for additional information. Thismay include a request for specific events, activity for specificcomputing objects, or events over a specific time frame, or somecombination of these. Thus for example, the threat management facility308 may request all changes to the registry of system information forthe past forty eight hours, all files opened by system processes in thepast day, all network connections or network communications within thepast hour, or any other parametrized request for activities monitored bythe data recorder 304. In another aspect, the entire data log, or theentire log over some predetermined window of time, may be request forfurther analysis at a remote resource.

It will be appreciated that communications among third party services320, a threat management facility 308, and one or more endpoints such asthe endpoint 302 may be facilitated by using consistent namingconventions across products and machines. For example, the system 300may usefully implement globally unique device identifiers, useridentifiers, application identifiers, data identifiers, Uniform ResourceLocators, network flows, and files. The system may also or instead usetuples to uniquely identify communications or network connections basedon, e.g., source and destination addresses and so forth.

According to the foregoing, a system disclosed herein includes anenterprise network, and endpoint coupled to the enterprise network, anda threat management facility coupled in a communicating relationshipwith the endpoint and a plurality of other endpoints through theenterprise network. The endpoint may have a data recorder that stores anevent stream of event data for computing objects, a filter for creatinga filtered event stream with a subset of event data from the eventstream, and a query interface for receiving queries to the data recorderfrom a remote resource, the endpoint further including a local securityagent configured to detect malware on the endpoint based on event datastored by the data recorder, and further configured to communicate thefiltered event stream over the enterprise network. The threat managementfacility may be configured to receive the filtered event stream from theendpoint, detect malware on the endpoint based on the filtered eventstream, and remediate the endpoint when malware is detected, the threatmanagement facility further configured to modify security functionswithin the enterprise network based on a security state of the endpoint.

The threat management facility may be configured to adjust reporting ofevent data through the filter in response to a change in the filteredevent stream received from the endpoint. The threat management facilitymay be configured to adjust reporting of event data through the filterwhen the filtered event stream indicates a compromised security state ofthe endpoint. The threat management facility may be configured to adjustreporting of event data from one or more other endpoints in response toa change in the filtered event stream received from the endpoint. Thethreat management facility may be configured to adjust reporting ofevent data through the filter when the filtered event stream indicates acompromised security state of the endpoint. The threat managementfacility may be configured to request additional data from the datarecorder when the filtered event stream indicates a compromised securitystate of the endpoint. The threat management facility may be configuredto request additional data from the data recorder when a security agentof the endpoint reports a security compromise independently from thefiltered event stream. The threat management facility may be configuredto adjust handling of network traffic at a gateway to the enterprisenetwork in response to a predetermined change in the filtered eventstream. The threat management facility may include a machine learningmodel for identifying potentially malicious activity on the endpointbased on the filtered event stream. The threat management facility maybe configured to detect potentially malicious activity based on aplurality of filtered event streams from a plurality of endpoints. Thethreat management facility may be configured to detect malware on theendpoint based on the filtered event stream and additional context forthe endpoint.

The data recorder may record one or more events from a kernel driver.The data recorder may record at least one change to a registry of systemsettings for the endpoint. The endpoints may include a server, afirewall for the enterprise network, a gateway for the enterprisenetwork, or any combination of these. The endpoint may be coupled to theenterprise network through a virtual private network or a wirelessnetwork. The endpoint may be configured to periodically transmit asnapshot of aggregated, unfiltered data from the data recorder to thethreat management facility for remote storage. The data recorder may beconfigured to delete records in the data recorder corresponding to thesnapshot in order to free memory on the endpoint for additionalrecording.

FIG. 4 illustrates a threat management system. In general, the systemmay include an endpoint 402, a firewall 404, a server 406 and a threatmanagement facility 408 coupled to one another directly or indirectlythrough a data network 405, all as generally described above. Each ofthe entities depicted in FIG. 4 may, for example, be implemented on oneor more computing devices such as the computing device described herein.A number of systems may be distributed across these various componentsto support threat detection, such as a coloring system 410, a keymanagement system 412 and a heartbeat system 414, each of which mayinclude software components executing on any of the foregoing systemcomponents, and each of which may communicate with the threat managementfacility 408 and an endpoint threat detection agent 420 executing on theendpoint 402 to support improved threat detection and remediation.

The coloring system 410 may be used to label or color software objectsfor improved tracking and detection of potentially harmful activity. Thecoloring system 410 may, for example, label files, executables,processes, network communications, data sources and so forth with anysuitable information. A variety of techniques may be used to selectstatic and/or dynamic labels for any of these various software objects,and to manage the mechanics of applying and propagating coloringinformation as appropriate. For example, a process may inherit a colorfrom an application that launches the process. Similarly, a file mayinherit a color from a process when it is created or opened by aprocess, and/or a process may inherit a color from a file that theprocess has opened. More generally, any type of labeling, as well asrules for propagating, inheriting, changing, or otherwise manipulatingsuch labels, may be used by the coloring system 410 as contemplatedherein.

The key management system 412 may support management of keys for theendpoint 402 in order to selectively permit or prevent access to contenton the endpoint 402 on a file-specific basis, a process-specific basis,an application-specific basis, a user-specific basis, or any othersuitable basis in order to prevent data leakage, and in order to supportmore fine-grained and immediate control over access to content on theendpoint 402 when a security compromise is detected. Thus, for example,if a particular process executing on the endpoint is compromised, orpotentially compromised or otherwise under suspicion, keys to thatprocess may be revoked in order to prevent, e.g., data leakage or othermalicious activity.

The heartbeat system 414 may be used to provide periodic or aperiodicinformation from the endpoint 402 or other system components aboutsystem health, security, status, and so forth. A heartbeat may beencrypted or plaintext, or some combination of these, and may becommunicated unidirectionally (e.g., from the endpoint 408 to the threatmanagement facility 408) or bidirectionally (e.g., between the endpoint402 and the server 406, or any other pair of system components) on anyuseful schedule.

In general, these various monitoring and management systems maycooperate to provide improved threat detection and response. Forexample, the coloring system 410 may be used to evaluate when aparticular process is potentially opening inappropriate files based onan inconsistency or mismatch in colors, and a potential threat may beconfirmed based on an interrupted heartbeat from the heartbeat system414. The key management system 412 may then be deployed to revoke keysto the process so that no further files can be opened, deleted, orotherwise modified. More generally, the cooperation of these systemsenables a wide variety of reactive measures that can improve detectionand remediation of potential threats to an endpoint.

FIG. 5 illustrates an event graph 500 stored by a data recorder such asany of the data recorders described herein. The event graph 500 mayinclude a sequence of computing objects causally related by a number ofevents, and which provide a description of computing activity on one ormore endpoints. The event graph 500 may be generated, for example, whena security event 502 is detected on an endpoint, and may be based on adata log or similar records obtained by an event data recorder duringoperation of the endpoint. The event graph 500 may be used to determinea root cause 504 of the security event 502 as generally described above.The event graph 500 may also or instead be continuously generated toserve as, or be a part of, the data log obtained by the data recorder.In any case, an event graph 500, or a portion of an event graph 500 in awindow before or around the time of a security event, may be obtainedand analyzed after a security event 502 occurs to assist in determiningits root cause 504. The event graph 500 depicted in the figure isprovided by way of example only, and it will be understood that manyother forms and contents for event graphs 500 are also or insteadpossible. It also will be understood that while the figure illustrates agraphical depiction of an event graph 500, the event graph 500 may bestored in any suitable data structure or combination of data structuressuitable for capturing the chain of events and objects in a manner thatpreserves causal relationships for use in forensics and malwaredetection as contemplated herein.

By way of example, the event graph 500 depicted in the figure beginswith a computing object that is a USB device 512, which may be connectedto an endpoint. Where the USB device 512 includes a directory or filesystem, the USB device 512 may be mounted or accessed by a file systemon an endpoint to read contents. The USB device 512 may be detected 513and contents of the USB device 512 may be opened 514, e.g., by a user ofthe endpoint or automatically by the endpoint in response to detectionof the USB device 512. The USB device 512 may include one or more filesand applications, e.g., a first file 516, a second file 518, and a firstapplication 520. The first file 516 may be associated with a first event522 and the second file may be associated with a second event 524. Thefirst application 520 may access one or more files on the endpoint,e.g., the third file 526 shown in the figure. The first application 520may also or instead perform one or more actions 528, such as accessing aURL 530. Accessing the URL 530 may download or run a second application532 on the endpoint, which in turn accesses one or more files (e.g., thefourth file 534 shown in the figure) or is associated with other events(e.g., the third event 536 shown in the figure).

In the example provided by the event graph 500 depicted in the figure,the detected security event 502 may include the action 528 associatedwith the first application 520, e.g., accessing the URL 530. By way ofexample, the URL 530 may be a known malicious URL or a URL or networkaddress otherwise associated with malware. The URL 530 may also orinstead include a blacklisted network address that although notassociated with malware may be prohibited by a security policy of theendpoint or enterprise network in which the endpoint is a participant.The URL 530 may have a determined reputation or an unknown reputation.Thus, accessing the URL 530 can be detected through known computingsecurity techniques.

In response to detecting the security event 502, the event graph 500 maybe traversed in a reverse order from a computing object associated withthe security event 502 based on the sequence of events included in theevent graph 500. For example, traversing backward from the action 528leads to at least the first application 520 and the USB device 512. Aspart of a root cause analysis, one or more cause identification rulesmay be applied to one or more of the preceding computing objects havinga causal relationship with the detected security event 502, or to eachcomputing object having a causal relationship to another computingobject in the sequence of events preceding the detected security event502. For example, other computing objects and events may be tangentiallyassociated with causally related computing objects when traversing theevent graph 500 in a reverse order—such as the first file 516, thesecond file 518, the third file 525, the first event 522, and the secondevent 524 depicted in the figure. In an aspect, the one or more causeidentification rules are applied to computing objects preceding thedetected security event 502 until a cause of the security event 502 isidentified.

In the example shown in the figure, the USB device 512 may be identifiedas the root cause 504 of the security event 502. In other words, the USBdevice 512 was the source of the application (the first application 520)that initiated the security event 502 (the action 528 of accessing thepotentially malicious or otherwise unwanted URL 530).

The event graph 500 may similarly be traversed going forward from one ormore of the root cause 504 or the security event 502 to identify one ormore other computing objects affected by the root cause 504 or thesecurity event 502. For example, the first file 516 and the second 518potentially may be corrupted because the USB device 512 includedmalicious content. Similarly, any related actions performed after thesecurity event 502 such as any performed by the second application 532may be corrupted. Further testing or remediation techniques may beapplied to any of the computing objects affected by the root cause 504or the security event 502.

The event graph 500 may include one or more computing objects or eventsthat are not located on a path between the security event 502 and theroot cause 504. These computing objects or events may be filtered or‘pruned’ from the event graph 500 when performing a root cause analysisor an analysis to identify other computing objects affected by the rootcause 504 or the security event 502. For example, computing objects orevents that may be pruned from the event graph 500 may include the USBdrive 510 and the USB device being detected 513.

It will be appreciated that the event graph 500 depicted in FIG. 5 is anabstracted, simplified version of actual nodes and events on an endpointfor demonstration. Numerous other nodes and edges will be present in aworking computing environment. For example, when a USB device is coupledto an endpoint, the new hardware will first be detected, and then theendpoint may search for suitable drivers and, where appropriate, presenta user inquiry of how the new hardware should be handled. A user maythen apply a file system to view contents of the USB device and select afile to open or execute as desired, or an autorun.exe or similar filemay be present on the USB device that begins to execute automaticallywhen the USB device is inserted. All of these operations may requiremultiple operating system calls, file system accesses, hardwareabstraction layer interaction, and so forth, all of which may bediscretely represented within the event graph 500, or abstracted up to asingle event or object as appropriate. Thus, it will be appreciated thatthe event graph 500 depicted in the drawing is intended to serve as anillustrative example only, and not to express or imply a particularlevel of abstraction that is necessary or useful for root causeidentification as contemplated herein.

The event graph 500 may be created or analyzed using rules that defineone or more relationships between events and computing objects. The CLanguage Integrated Production System (CLIPS) is a public domainsoftware tool intended for building expert systems, and may be suitablyadapted for analysis of a graph such as the event graph 500 to identifypatterns and otherwise apply rules for analysis thereof. While othertools and programming environments may also or instead be employed,CLIPS can support a forward and reverse chaining inference enginesuitable for a large amount of input data with a relatively small set ofinference rules. Using CLIPS, a feed of new data can trigger a newinference, which may be suitable for dynamic solutions to root causeinvestigations.

An event graph such as the event graph 500 shown in the figure mayinclude any number of nodes and edges, where computing objects arerepresented by nodes and events are represented by edges that mark thecausal or otherwise directional relationships between computing objectssuch as data flows, control flows, network flows and so forth. Whileprocesses or files are common forms of nodes that might appear in such agraph, any other computing object such as an IP address, a registry key,a domain name, a uniform resource locator, a command line input or otherobject may also or instead be designated to be a node in an event graphas contemplated herein. Similarly, while an edge may be formed by an IPconnection, a file read, a file write, a process invocation (parent,child, etc.), a process path, a thread injection, a registry write, adomain name service query, a uniform resource locator access and soforth other edges may be designated. As described above, when a securityevent is detected, the source of the security event may serve as astarting point within the event graph 500, which may then be traversedbackward to identify a root cause using any number of suitable causeidentification rules. The event graph 500 may then usefully be traversedforward from that root cause to identify other computing objects thatare potentially tainted by the root cause so that a more completeremediation can be performed.

FIG. 6 depicts a Sensors, Events, Analytics, and Response (SEAR)environment, which may be used on a compute instance 620 such as amanaged device. The compute instance 620 may include sensors 631, 632,633, 634 that produce data that are recognized as events according tothe entity model. The sensors 631, 632, 633, 634 thus are sources ofevent information. The output of sensors 631, 632, 633, 644 may beobjects 642 that are recognized as events 644. There may be multipleobjects 642, 646 and events 644, 648 provided by a sensor. The eventsmay be processed by a local event processing facility 654. The eventprocessing may perform tokenizing and processing. Some events may berecognized and evaluated in real-time, other events may be evaluated inthe context of other events. This may be stream or bulk processing.Events may have attributes (e.g., mandatory, optional (e.g., besteffort), sensitive (tokenize it in local event store)), or associatedcontextual information.

A local event recorder 650 may be part of the event logging facility.Some recorded events may be stored locally and some may be communicatedto another compute instance, such as the cloud. Some events will all besent in real time, some only stored locally (and should be retrievable).An event filter 662 may be used to parse the events. Local analytics 664on a compute instance may be used to locally identify events ofinterest. A communication facility 660 will communicate events to acentral event store, such as a threat management facility 610, which maybe a cloud facility. Local enforcement 666 may be used to take steps inresponse to events, as determined by the policy management facility 666.In embodiments, events can have attributes (e.g., mandatory, optional(e.g., best effort), sensitive (e.g., tokenize it in local eventstore)). Some events will all be sent in real time, some only storedlocally (and should be retrievable).

A goal may be to discover as much as we can about the assets in theenterprise, and reduce surprises, such as compute instances that networkadministrators are not aware of, or unpatched compute instances, orvaluable data leaving the enterprise.

As one non-limiting example, static policies may be assigned to accessof files and data. Events involving files and data may be observed bysensors, for example, in a file system filter, generating events. Theevents may be determined to be of interest based on the policies.

FIG. 7 depicts centralized event collection. Referring to FIG. 7,centralized event collection 700 may be used to receive and store eventsfrom various compute instances. Events are received at a threatmanagement facility 710 by event collection 762. Events may be receivedfrom compute instances, shown for the sake of clarity of illustration asa device 711, a device 712, a device 713, and a firewall 714, althoughevents may be received from any number or type of compute instances.Events may be stored in the event store 764, and also may be processedin real-time by the stream processing facility 766. The entity models770 may be used by the analytics facility 768 to make observations andinferences based on the events.

In embodiments, events are continuously analyzed against a baseline. Thebaseline may be adjusted to account for normal behavior. Comparison tobaselines may include looking for outliers and anomalies as well asimpossible events. For example, if a user logs on from Germany and thenlogs in from San Francisco, that may be considered impossible.Comparisons may be made at different levels. For example, the entity maybe compared to itself e.g., does this user on Monday compare to pastactivity. For example, the entity may be compared to its peer group,e.g., is a finance department member behaving similar to others. Forexample, the entity may be compared to other entities within theenterprise. For example, the entity may be compared to other users atsimilar enterprises in the same industry, or in the same location, aswell as to the universe of all users.

Real-time and retrospective threat intelligence may also be included, aswell as vulnerability information and patch information.

With a sufficient level of confidence in the inferences, active,adaptive responses may be taken. For example, dynamic policies 771 maybe updated to better fit the security profile to the environment thathas been discovered and observed, e.g., by adjusting security settingswithin a security policy or group of security policies. A policyenforcement facility 773 may enforce these updated dynamic policies 771at compute instances, such as the compute instances 711-714.

In embodiments, high-interaction interfaces allow an admin to interactwith the event store 764 to better understand the assets in theenterprise facility and for specific purposes, such as threat hunting.

FIG. 8 shows a flow chart of a method for computer augmented threatevaluation. In general, an automated system attempts to characterizecode as safe or unsafe. For intermediate threat samples that are notplaced with sufficient confidence in either category, human-readableanalysis is automatically generated, such as qualitative or quantitativecomparisons to previously categorized threat samples, in order to assista human reviewer in reaching a final disposition. For example, a randomforest over human-interpretable features may be created and used toidentify suspicious features in a manner that is understandable to, andactionable by, a human reviewer. Similarly, a k-nearest neighboralgorithm or similar technique may be used to identify similar samplesof known safe and unsafe code based on a model for one or more of a filepath, a URL, an executable, and so forth. Similar code may then bedisplayed along with other information to a user for evaluation in auser interface. This comparative information can substantially improvethe speed and accuracy of human interventions by providing richercontext for human review of potential threats.

As shown in step 802, the method 800 may include providing a model suchas a threat detection model for evaluating a likelihood that a threatsample is at least one of safe or malicious based on a training set ofknown threat samples. This may include any of the machine learningmodels or other threat detection models contemplated herein. As shown instep 804, the method 800 may also include providing threat samples suchas samples of code that are known to be safe and samples of code thatare known to be malicious. This may also or instead include known safeand unsafe samples of network activity, file content, file activity,behaviors, events, and so forth. The threat detection model may includea machine learning model trained using these threat samples, or anyother suitable training set, or some combination of these. Thus,providing the model may include training a machine learning model toidentify malicious code in a training set including threat samples thatare known to be safe and known to be malicious.

The model may include a model for evaluating a likelihood that a threatsample is at least one of safe or malicious based on a training set ofknown threat samples. The model may also or instead include anintegrative model that evaluates a potential threat by a threat samplebased on a combination of a first model configured to identify maliciouscode based on behavioral tags, a second model configured to identifymalicious code based on an executable file path, and a third modelconfigured to identify malicious code based on a Uniform ResourceLocator within the threat sample, or any of the other integrative modelscontemplated herein.

As shown in step 806, the method 800 may include identifyingintermediate threats. For example, this may include identifying a newthreat sample as an intermediate threat that is not within apredetermined likelihood of being malicious or safe according to themodel, or using any of the other techniques described herein.

As shown in step 808, the method 800 may include identifyingsupplemental information relevant to evaluation of the new threatsample, such as relevant features of the new threat sample contributingto an inference of malicious code.

For example, the method 800 may include identifying one or morefeatures, such as relevant features of the new threat sample associatedwith an inference of malicious code, using a random forest overhuman-interpretable features associated with an inference of maliciouscode in the training set of known threat samples (or any other suitabletraining set or the like). Random forests or random decision forests arean ensemble learning method for classification, regression, and othertasks, that operate by constructing a multitude of decision trees attraining time and outputting the class that is the mode of the classes(classification) or mean prediction (regression) of the individualtrees. As a significant advantage, the structure of the decision tree(s)can be organized around human-interpretable features such as whether athreat sample is signed or whether the threat sample opens new filesduring execution. While the creation of a random forest is generallycomputationally expensive, and other more efficient techniques are knownfor automated classification, the output of a random forest overhuman-interpretable features can provide highly useful context to ahuman reviewer when evaluating intermediate threats as contemplatedherein, and thus provides particular advantages over otherclassification techniques in this context, even when used in addition toother (possibly more computationally efficient) classification modelsand techniques for evaluating riskiness of unknown threat samples.

Identifying supplemental information may also or instead includeidentifying similar threat samples known to be safe or maliciousincluding one or more safe threat samples similar to the new threatsample and one or more malicious threat samples similar to the newthreat sample. In this context, similarity may usefully be computedbased on a k-nearest neighbor algorithm. The similar threat samples may,for example, include a list of safe threat samples ranked based onsimilarity to the new threat sample according to the k-nearest neighboralgorithm, which may in turn be presented as a ranked list in a userinterface. The similar code may also or instead include a list ofmalicious threat samples ranked based on similarity to the new threatsample according to the k-nearest neighbor algorithm. Using these rankedlists, a user may advantageously be presented with an ordered list ofnearest, known safe threat samples and nearest, known unsafe samples. Ak-nearest neighbor algorithm is a non-parametric method that assigns anew item to a particular class based on a closest neighbor within a(usually multi-dimensional) features space for training data.

While this approach provides a computationally efficient technique forevaluating similarity for certain data types, it will be understood thatother computational measures of similarity are known in the art, and mayusefully be employed to evaluate similarity of a new threat sample toknown safe an unsafe threat samples as contemplated herein. For example,a nearest centroid classifier or nearest prototype classifier uses aclassification model that assigns a classification based on a closestcentroid that may be used to assess similarity as contemplated herein.As another example, an n-gram analysis supports efficient approximatematching and may be used to perform fast, large scale similarityanalysis for a given file path over a large database of known maliciousand known benign file paths and URLs.

While certain portions of this description emphasize the analysis ofexecutables for detection of suspiciousness or the identification ofintermediate threats, it should be understood that the term “threatsample” is not so limited. Other threat samples based on, e.g., files,caches, or other data sources may be used. Events, e.g., in a filteredevent stream may also or instead be used, and the techniques describedherein for use with code samples are also generally applicable to otherthreat samples instead of explicit computer code such as networkactivity, content, event streams that identify activities or behaviors,and so forth. Thus for example, activities such as visiting a particularURL, opening an attachment, sending an electronic mail, or other eventsmay also or instead be analyzed as threat samples by an integrativemodel or other threat detection tools to identify potential malwarethreats on an endpoint or group of endpoints.

As shown in step 810, the method 800 may include displaying theintermediate threat(s) and supplemental information in a user interfacefor user disposition, or otherwise augmenting a description of the newthreat sample in a user interface with the supplemental information.This may, for example, include presenting a description of the newthreat sample, the one or more relevant features, and the similar threatsamples in a user interface. In one aspect, the method may includedisplaying a list of the similar threat samples ranked according tosimilarity to the new threat sample using, e.g., a k-nearest neighboralgorithm or any other suitable technique for measuring similarity. Thismay, for example, include similarity of executable code, similarity ofbehaviors, similarity of filenames, similarity of URL's called, orsimilarity of any other objective feature or combination of featuresthat can be correlated to risk (or lack of risk). In one aspect, anumber of the most similar safe samples and a number of the most similarunsafe samples may be presented together, and ranked, e.g., based onrelative threat or based on similarity. The threat samples may bedisplayed along with descriptive information, attributes, behavioralcharacteristics, metadata and so forth, as well as any other informationthat might help a human user assess relative similarity when disposingof the current, new threat sample.

More generally, any supplemental information that might be helpful to auser in assessing a new threat sample may usefully be gathered anddisplayed to the user. For example, this may include augmenting thedescription of the new threat sample with a reputation of the new threatsample, e.g., based on reputation information available from a threatmanagement facility. This may also or instead include augmenting thedescription of the new threat sample with a suspiciousness score basedon a genetic analysis of features of the new threat sample. In anotheraspect, this may include augmenting the description of the new threatsample with contextual information such as users, related processes,associated data sources or files used by the threat sample, signatureanalysis, behavioral analysis, software update history or status for theendpoint, and so forth.

As shown in step 812, the method 800 may include disposing of theintermediate threat(s), such as by receiving user input through the userinterface categorizing the new threat sample as safe, unsafe, orundetermined. Thus, in one aspect, the user interface may be configuredto receive a user input categorizing the new threat sample as safe,unsafe, or undetermined. Where a disposition as unsafe does notautomatically initiate a remedial action, the user interface may also beconfigured to receive an express instruction for a remedial action suchas any of the remedial actions described herein, or any other actionssuitable for disposing of or otherwise managing a new threat. In anotheraspect, the user interface may be configured to receive user input toadjust filtering of an event stream from an endpoint that provided thenew threat sample, which may permit an increase or decrease in theamount of event reporting from the endpoint instead of, or in additionto, a specific characterization of the new threat sample.

In another aspect, a system as contemplated herein includes a memorystoring a first model for evaluating a likelihood that a threat sampleis at least one of safe or malicious, a second model characterizing amanner in which a number of human-interpretable features contribute toan evaluation of suspiciousness of a file, and a third model forevaluating similarity of threat samples. The system may include a threatmanagement facility including a processor configured to apply the firstmodel to identify a new threat sample as an intermediate threat when thenew threat sample is not within a predetermined likelihood of beingmalicious or safe according to the first model. The system may alsoinclude a web server configured to present a user interface including adescription of the intermediate threat, augmented by one or morefeatures of the intermediate threat identified with the second model andone or more similar threat samples identified with the third model, theweb server further configured to receive input from a user through theuser interface disposing of the intermediate threat. Disposing of theintermediate threat may include remediating the intermediate threat.Disposing of the intermediate threat may also or instead includecharacterizing the intermediate threat as safe, unsafe, or undetermined.

FIG. 9 shows a user interface for managing intermediate threats in anenterprise network. The user interface 900 may be provided, e.g., as aweb page or other content presented from the threat management facilityfor display on a user device such as an end user endpoint. The userinterface 900 may show a feed 902 of suspicious events. The eventswithin this feed 902 may be sorted, e.g., into files, URL visits,executables, processes, downloads, and so forth, or any other usefulcategories for review, or the events may be combined into a single feed.As noted above, threat samples may include executable code, however, thetechniques contemplated herein may also or instead be applied to threatsamples such as files, network activity, or streams of event data.

A variety of tools 904 for explicit disposition of new threat samplesmay be provided. For example, the user interface 900 may include tools904 such as buttons or similar controls for a user to mark a particularevent as, e.g., safe, unsafe, low priority, unknown, or the like. Theuser interface 900 may also provide controls for querying the enterprisenetwork for additional information, for adjusting filtering of eventstreams from endpoint data recorders, for initiating scans or otheranalysis, and so forth.

In one aspect, the user interface 900 may display a window 906 with moregranular information about features contributing to suspiciousness. Forexample, an analysis of a threat sample may return a 90% suspicion ofmalicious code, while a file path analysis may return a 57% suspicion,and a URL analysis may return a 77% suspicion. While an integrativemodel may combine these various features into a single estimate ofsuspiciousness or potential risk, the individual values may be useful toa user attempting to manually dispose of an intermediate threat.Furthermore, for any particular feature (e.g., the URL analysis in FIG.9), a number of most similar events or threat samples for that featuremay be displayed, with similarity evaluated using, e.g., a k-nearestneighbor algorithm or other algorithm for evaluating similarity within afeature space. These more granular estimates of suspiciousness may bepresented in separate sub-windows, which may usefully be arranged in anaccordion, a stacked group of drop-down lists, or any other suitablecontrol element or combination of control elements that permits eachtype of estimate to be expanded or collapsed under user control.

FIG. 10 shows a user interface for managing intermediate threats in anenterprise network. The user interface 1050 may, for example, includeany of the user interfaces described herein.

In one aspect, the user interface 1050 may show a window 1052 listinghuman interpretable features contributing to an estimate ofsuspiciousness. For example, the user interface 1050 may presentparticular features in the window 1052 such as whether a threat sampleis signed, whether the threat sample calls cryptographic libraries, andwhether the threat sample inspects other processes. For each suchfeature, the user interface 1050 may further present the number of knowngood and known bad threat samples for that feature, with the featuresprogressively nested according to the hierarchy of a random decisionforest.

The features displayed in this list may be a subset of features in arandom forest over human-interpretable features that is selected basedon relevance, e.g., how strongly indicative those features are of safetyor suspiciousness. In one aspect, this may include features that aremost heavily weighted on a percentage basis toward safety orsuspiciousness. In another aspect, this may include features with thelargest number of relevant samples (e.g., higher up the decision tree).In another aspect, these and any other factors may be weighted orotherwise collectively evaluated to select a subset of features fordisplay to a user. This approach may usefully assist a human user whenevaluating an intermediate threat for manual disposition by providing adisplay of features that contribute more significantly or mostsignificantly to the potential risk associated with a threat sample.

In another aspect, the user interface may provide a display of therandom forest output (e.g., quantitative data about varioushuman-interpretable features), or a display of most similar safe andunsafe threat samples, or some combination of these. For example, theuser interface may provide one or more user controls for the user toselect among these different analyses, and/or other analyses, contextualinformation, or other supplemental information.

FIG. 11 shows a system for event monitoring and response. In general,the system may include a number of compute instances 1102 that use localsecurity agents 1108 to gather events 1106 from sensors 1104 into eventvectors 1110, and then report these event vectors 1110 to a threatmanagement facility 1112. The threat management facility 1112 may storethe event vectors 1110 from a number of compute instances 1102 as a datastream 1114 in a data repository 1116 such as a memory or other datastore of the threat management facility 1112. The event stream 1114 maybe analyzed with an analysis module 1118, which may in turn createentity models 1120 useful for detecting, e.g., unexpected variations inbehavior of compute instances 1102. A detection engine 1122 may beapplied to the event stream 1114 in order to detect unusual or maliciousactivity, e.g. based on the entity models 1120 or any other techniques.Where appropriate, the threat management facility 1112 may deployresponses to the compute instances 1102 using a response facility 1124.

The compute instances 1102 may be any of the compute instances describedherein, including without limitation any physical device such as alaptop, desktop, gateway, router, firewall, smartphone, tablet, or thelike, as well as a virtualized instance of any of the foregoing or anyother computer, user device, container, or the like. The sensors 1104and events 1106 may also generally be any of the sensors and eventsdescribed herein. The local security agent 1108 may be any of thesecurity agents described herein, or any other software component or thelike executing on or in association with one of the compute instances1102 to locally manage security of the compute instance and/orcoordinate security services with the threat management facility 1112and other remote resources.

The local security agent 1108 may collect events 1106 from sensors 1104on the compute instance 1102, and form the collected events 1106 intoevent vectors 1110 for communication to the threat management facility1112. The sensors 1104 and/or local security agent 1108 may usefullyprocess events 1106 in a number of ways in order to facilitatecommunication, computational efficiency, or downstream processing. Forexample, events 1106 may be tokenized. That is, a process that causes orcreates an event 1106 may be assigned a number or other identifier,which may be used locally by a compute instance or globally within theenterprise to identify a particular, known process. An event 1106 mayalso encode (tokenized or otherwise) a relationship among differentprocesses. For example, for a particular process that caused an event1106, a parent-child relationship or other dependency with otherprocesses may be encoded by providing process identifiers or the likewithin the event 1106, along with information characterizing therelationship among the processes. A Uniform Resource Locator or otherinformation for identifying resources or network locations may also betokenized or otherwise processed to support efficiency, consistency, andthe like. For example, a URL may be encoded in an event 1106 as a hashof a URL, or as a portion of a URL, or some combination of these (e.g.,a literal encoding of the top level domain, and a hash of some or all ofthe remaining path information). Other events 1106 such as registrychanges, system calls, remote procedure calls and the like may beliterally encoded into an event 1106 where they are relatively compact,or identified using any suitable tokenization, compression, or the like.

Other techniques may also or instead be used. For example, user-specificor machine-specific information may be altered where appropriate toanonymize the event vectors 1110 and mitigate exposure of sensitiveinformation during network communications. An event vector 1110, orindividual events 1106 therein, may also or instead be encrypted inorder to secure the contents against malicious interception. In anotheraspect, the events 1106 or event vectors 1110 may be compressed toconserve network resources. The event vectors 1110 may also or insteadbe prioritized, e.g., in order to increase sensitivity and decreaseresponse times for event vectors 1110 associated with a high likelihoodof malicious activity. In this latter aspect, the local security agent1108 may locally analyze events 1106 and/or event vectors 1110 in orderto permit suitable prioritization, as well as to support local detectionand response to malicious, or potentially malicious activity.

It will also be appreciated that events 1106 and/or event vectors 1110may usefully be labelled in a variety of ways. While labeling withprocess identifiers is described above, this may also or instead includean identification of an entity associated with the event 1106 or eventvector 1110. In this context, the entity may be any physical, logical,or conceptual entity useful for monitoring activity of compute instances1102 as described herein. For example, the entity may include a user, aphysical device, a virtualized machine, an operating system, anapplication, a process, a hardware subsystem (e.g., a network interfacecard, USB drive, camera, etc.), a network resource, a domain controller,a remote software service, and so forth. It should also be understoodthat the various entity types may be concurrently associated with aparticular event 1106, sensor 1104, or event vector 1110, or particularevents 1106 may be associated with multiple entities or event vectors1110. Thus for example, storing a file may be an event 1106 associatedwith a particular user, a particular machine, a particular operatingsystem, a particular physical storage device, and so forth.

In one aspect, the event vectors 1110 may be organized around entities.Thus for example, a request for access to a network resource may be anevent 1106. When such a request is initiated by a user, an event vector1110 for that user may be created and reported along with othertemporally adjacent or otherwise related events 1106 associated withthat user. Where the network request involves an interaction with, e.g.,an authentication and identity management system, this may berepresented as another entity, or as an event 1106 (or group of events1106) in the event vector 1110 for the user. At the same time, a secondevent vector 1110 for the compute instance 1102 may also be created andreported along with other temporally adjacent or otherwise relatedevents 1106 associated with that compute instance 1102. Alternatively,the event vectors 1110 may be organized around chronology. That is,groups of events 1106 within a window of time may be reported as anevent vector 1101. The event vectors 1110 may also or instead beorganized around other aspects of the system 1100, such as particularsensors 1104 or groups of sensors 1104, causal relationships amongevents 1106, particular triggers, types of activity (e.g., networkcommunications, operating system, processes, etc.) and so forth. Ingeneral, the source of each event 1106, such as a particular sensor1104, or some entity, computing object or the like associated with thesensor 1104, may be encoded with the event 1106 to permit explicitidentification by the threat management facility 1112 or otherdownstream processing resources. Although depicted in FIG. 11 as havingsimilar size, it will also be understood that the event vectors 1110 maybe any size, and may usefully encode any number of different events1106.

The event vectors 1110 may be received by the threat management facility1112 and stored as an event stream 1114 in a data repository 1116, whichmay be any data store, memory, file or the like suitable for storing theevent vectors 1110. The event vectors 1110 may be time stamped orotherwise labeled by the threat management facility 1112 to recordchronology. In general, the event stream 1114 may be used for analysisand detection as further described herein.

In general, an analysis module 1118 may analyze the event stream 1114 toidentify patterns of events 1106 within the event stream 1114 useful foridentifying unusual or suspicious behavior. In one aspect, this mayinclude creating entity models 1120 that characterize behavior ofentities, such as any of the entities described herein. Each entitymodel 1120 may, for example, include a multi-dimensional description ofevents 1106 for an entity based on events 1106 occurring over time forthat entity. This may be, e.g., a statistical model based on a historyof events 1106 for the entity over time, e.g., using a window or rollingaverage of events 1106.

The entity models 1120 may, for example, be vector representations orthe like of different events 1106 expected for or associated with anentity, and may also include information about the frequency, magnitude,or pattern of occurrence for each such event 1106. In one aspect, theentity model 1120 may be based on an entity type (e.g., a particulartype of laptop, or a particular application), which may have a relatedevent schema that defines the types of events 1106 that are associatedwith that entity type. This may usefully provide a structural model fororganizing events 1106 and characterizing an entity before any eventvectors 1110 are collected, and/or for informing what events 1106 tomonitor for or associate with a particular entity.

As an event stream 1114 is collected, a statistical model or the likemay be developed for each event 1106 represented within the entity modelso that a baseline of expected activity can be created. In one aspect,an existing model may be used, e.g., when the entity or entity type isalready known and well characterized. The entity model may also orinstead be created by observing activity by the entity (as recorded inthe event stream 1114) over time. This may include, for example,monitoring the entity for an hour, for a day, for a week, or over anyother time interval suitable for creating a model with a sufficientlikelihood of representing ordinary behavior to be useful as a baselineas contemplated herein. In one practical example, certain softwareapplications have been demonstrated to yield a useful baseline withinabout two weeks. It will also be understood that, once an entity modelis created, the entity model may usefully be updated, which may occur atany suitable intervals according to, e.g., the length of time to obtaina stable baseline, the amount of activity by the entity, the importanceof the entity (e.g., to security, operation of a compute instance 1102,and so forth), or any other factors.

These techniques may be used to create an entity model 1120 for any ofthe entities described herein, including without limitation physicalhardware items, virtualized items, software items, data and date stores,programming interfaces, communications interfaces, remote resources, andso forth, or any of the other entities, computing objects, assets or thelike described herein. In one aspect, the entities may be arrangedaround a conceptual stack for an endpoint in an enterprise network, suchas by providing entities for a domain controller, a compute instance, auser, an operating system, a library, an application, a process, anddata. This may also or instead include any of a number of physicaldevices such as a laptop, a desktop, a gateway, a router, a firewall, asmartphone, a tablet, a personal computer, a notebook, a server, amobile device, an IoT device. The entity may also or instead includehardware subsystems such as a peripheral, a keyboard, a mouse, adisplay, a network interface card, a USB drive, a camera, a disk driveor other physical storage device, and so forth. The entity may also orinstead include a virtualized instance of any of these physical devicesor systems, or any other virtualized compute instance or other computingresource such as a virtual machine, a hypervisor, or the like. Inanother aspect, this may include computing objects or resources such asa container, an operating system, a library, an application, a process,a file or other data, or the like. An entity may also or instead includeremote resources, such as a cloud computing resource, cloud dataresource, remote software service, or any other network resource or thelike. An entity may also include other entities such as a user orrelated identity, or more specific system resources such as a kerneldriver, system registry, process cache, and so forth. More generally,any physical, virtual, logical, or other computing resource, asset, orthe like that can usefully be instrumented and/or monitored to provideevents for use as contemplated herein may be an entity as that term isused in this description.

As noted above, the entities of interest here may exist non-exclusivelyat various levels of hardware and software abstraction, and the entitymodels may similarly be of varying and overlapping scope. By way of anon-limiting example, an entity model for a laptop may includeapplications running on the laptop. In one aspect, the entity model mayincorporate all network activity by the laptop, while in another aspect,network activity may be associated with the entity models for specificapplications. Or the network activity may be associated with bothentities, e.g., such that a single event is incorporated into multipleevent vectors associated with multiple entities. In general, thesedesign choices may affect the granularity of detections, the amount ofprocessing and communications overhead, and so forth, and any suchvariations consistent with deployment within an enterprise network ascontemplated herein are intended to fall within the scope of thisdisclosure.

According to the foregoing, in one aspect an entity model may contain aschema or the like describing events associated with an entity (or atype of entity), along with information about normal or expectedbehavior for each event 1106 associated with the entity. In one aspect,an entity type (e.g., laptop, or laptop by manufacturer X, or virtualmachine in environment Y) may be used to select a schema for an entitymodel, while activities of a particular instances of that entity typemay be used to generate the baseline for the entity model used indetections and the like. Thus, for example, if a user installs an officeproductivity suite, an entity model for that entity type may be selectedbased on the types of events 1106 known to be associated with the usethe application, or the capabilities of the application. However,different users may use the software differently, so the baseline ofexpected behavior may be evaluated for a particular installation of theapplication by monitoring activity of the application over time. Inanother aspect, the schema for an entity model may itself be extensible.That is, the schema of different events 1106 may be created based onobservations of activity associated with the entity. When a new type ofevent 1106 is detected for that entity, the event 1106 may be added tothe schema for a corresponding entity type.

Once an entity model 1120 has been created and a stable baselineestablished, the entity model 1120 may be deployed for use in monitoringprospective activity. This monitoring may, for example, use the sameevent stream 1114 that was used to create the entity model 1120, or afiltered or otherwise processed version of the event stream 1114. Itwill be appreciated that the entity models 1120 may generally bedeployed as fixed or relatively static or discrete models, or any one ormore of the entity models 1120 may be continuously updated so that theychange over time as new information becomes available, e.g., in theevent stream 1114 or otherwise.

The detection engine 1122 may compare new events 1106 generated by anentity, as recorded in the event stream 1114, to the entity model 1120that characterizes a baseline of expected activity. By representing theentity model 1120 and the event vectors 1110 in a common, or related,vector space, deviations from expected behavior can usefully beidentified based on the vector distance between one or more eventvectors 1110 and the entity model 1120. This comparison may usefullyemploy a variety of vector or similarity measures known in the art. Forexample, the comparison may use one or more vector distances such as aEuclidean distance, a Mahalanobis distance, a Minkowski distance, or anyother suitable measurement of difference within the corresponding vectorspace. In another aspect, a k-nearest neighbor classifier may be used tocalculate a distance between a point of interest and a training dataset, or more generally to determine whether an event vector 1110 shouldbe classified as within the baseline activity characterized by theentity model.

It will be understood that, while event vectors 1110 and entity models1120 as described herein provide one useful technique observingdeviations from a baseline of expected behavior by entities within anenterprise, the detection engine 1122 may also or instead employ otherdetection techniques based on the event stream 1114, e.g., to supportreal time detection of suspicious or malicious behavior. For example,certain events 1106 may be independently and directly indicative ofmalicious activity, such as initiating communications with a knowncommand and control center for an advanced persistent threat. Otherevents 1106 may be potentially indicative of malicious activity, such asinitiating disk-wide encryption or transmitting sensitive informationfrom an endpoint. While tools exist for detecting these types ofmalicious activity, relevant events 1106 may be present in the eventstream 1114, and the response facility 1124 may usefully triggeradditional analysis, investigation, or other responses based on theevent stream 1114 instead of or in addition to monitoring for deviationsfrom entity baselines. In another aspect, concurrent deviations bydifferent entities, or a pattern of deviations for a single entity oramong entities, may also be usefully monitored. For example, a deviationin the behavior of a trusted application across multiple computeinstances 1102, either concurrently or in succession, may indicate arollout of a software update rather than malicious behavior. Conversely,if a number of compute instances 1102 concurrently begin contacting anunknown network address, this may be an indication of malwarepropagating among devices in an enterprise network. More generally,deviations among different entities, or among multiple instances of aparticular entity, may provide useful information about actual orpotential causes of the change, and may inform subsequent manual orautomated investigations.

In general, where the event stream 1114 deviates from a baseline ofexpected activity that is described in the entity models 1120 for one ormore entities, any number of responses may be initiated by the responsefacility 1124 of the threat management facility 1112. In one aspect,this may include deployment of known remediations for malicious activitysuch as quarantine, termination of network communications, terminationof processes or applications, an increase in local monitoring activityon affected compute instances 1102, messages to a network administrator,filtering of network activity, antivirus scans, deployment of securitypatches or fixes, and so forth. This may also in policy updates. Forexample, security policies for compute instances 1102, users,applications or the like may be updated to security settings that imposestricter controls or limits on activity including, e.g., limits onnetwork activity (bandwidth, data quotas, permitted network addresses,etc.), limits on system changes (e.g., registry entries, certain systemcalls, etc.), limits on file activity (e.g., changes to filepermissions), increased levels of local activity monitoring, and soforth.

FIG. 12 shows a flow chart of a method for dynamic filtering of endpointevent streams. In general, activity on an endpoint is monitored in twostages with a local agent. In a first stage, particular computingobjects on the endpoint are selected for tracking. In a second stage,particular types of changes to those objects are selected. By selectingobjects and object changes in this manner, a compact data stream ofinformation highly relevant to threat detection can be provided from anendpoint to a central threat management facility. In order to supportdynamic threat response, the locus and level of detection applied by thelocal agent can be controlled by the threat management facility.

As shown in step 1202, the method 1200 may include instrumenting theendpoint, e.g. with a local agent, to detect a plurality of types ofchanges to a plurality of computing objects. In general, the changes maybe any of the events or other actions described herein, and thecomputing objects may be any of the computing objects described herein.For example, the computing objects may include a number of files, anumber of processes, and/or a number of executables. The computingobjects may also or instead include one or more of an electroniccommunication, a registry of system settings, a secure kernel cache, orany other data or data structure stored on an endpoint or communicatedto or from the endpoint. Similarly, the types of changes may be anytypes of changes that might usefully be monitored in a threat managementcontext as contemplated herein. For example, the endpoint may beinstrumented to detect file reads and writes, but not file opens orcloses. Or the endpoint may be instrumented to monitor inbound andoutbound electronic mail, but not outbound electronic mail to otherusers within the enterprise. As another example, the endpoint may beinstrumented to monitor changes to operating system registry entries bynon-system processes, or to monitor read/write activity thatsubstantially increases file entropy. More generally, any types ofchanges that might contribute to a determination of suspiciousness orsafety can usefully be monitored, with instrumentation of suitable,corresponding computing objects, all as contemplated herein.

As shown in step 1204, the method 1200 may include creating an eventstream from the local agent including each type of change to each of thecomputing objects detected on the endpoint.

As shown in step 1206, the method 1200 may include storing the eventstream in a data recorder on the endpoint. This may generally be anunfiltered event stream containing additional event data not includingin a filtered event stream that is sent to a threat management facility,and may include some or all of the event data that the endpoint isinstrumented to detect. For example, the unfiltered event stream mayinclude additional ones of the plurality of types of changes to theplurality of computing objects in a filtered event stream, or changes toadditional ones of the plurality of computing objects not included inthe filtered event stream.

As shown in step 1208, the method 1200 may include processing the eventstream with a filter at the endpoint to provide a filtered event streamincluding a subset of the types of changes to a subset of the computingobjects. In one aspect, the subset of computing objects includes one ormore of a file, an executable, a process, a database, and a message. Inanother aspect, the types of changes include at least one of a fileread, a file write, a file copy, a file encrypt, a file decrypt, anetwork communication, a registry update, a software installation, achange in permissions, and a query to a remote resource. It will beunderstood that, while the filtered event stream is illustrated asflowing from the event stream stored by the data recorder, the filteredevent stream may also or instead be created directly by a security agentas the unfiltered event stream is captured and forwarded to the datarecorder for storage.

Processing the event stream with the filter may also include locallyadjusting the filter at the endpoint, e.g., in response to local changesdetected on or by the endpoint. For example, the level of filtering maybe locally adjusted by the endpoint based on a reputation score for oneor more processes, files, or the like on the endpoint. This filteringmay be done for all detectable events on the endpoint, or for specificprocesses. Thus, for example, when a reputation for a new process orother computing object is unknown, the endpoint may decrease filteringto provide greater data reporting to the threat management facility forthat particular process. Thus, while step 1216 below contemplatescontrolling the filter from a central threat management facility or thelike, the filter may also or instead be controlled locally on anendpoint in response to changes in security posture, policy complianceposture, or any other events, context, malware detections, and so forth.

In one aspect, the filtered event stream may be arranged around anchorpoints such as a file, a domain name, or any other useful piece of dataor metadata for which the presence can be monitored on an endpoint. Forexample, a file hash may be created for a file and used to test for thepresence of that file on endpoints throughout an enterprise. Wheneverthis anchor point, e.g., the corresponding file hash, is detected on anendpoint, a collection of related events, metadata, context and so forthmay be added to the filtered event stream for reporting to a centralthreat management facility.

In another aspect, the level of filtering may be locally controlledbased on factors or requirements other than threat detection. Forexample, an event stream may be filtered to remove personal identifyinginformation, e.g., for compliance with data privacy regulations. Asanother example, filtering may be controlled based on network usagerestrictions, e.g., so that a particular endpoint does not exceed apredetermined hourly, daily, or weekly quota of bandwidth for eventreporting.

Further, it will be understood that the filtered event stream mayinclude synthetic events that characterize other collections of eventsin a single event or condensed group of events. This approachadvantageously permits more compact communication of relevantinformation to a threat management facility, as well as more compactstorage of information on the endpoint. In one aspect, the syntheticevents may be stored by the data recorder in place of (e.g., to reducememory requirements) or in addition to (e.g., to reduce communicationsrequirements while preserving a more complete log or related activity)more detailed logging of granular events on the endpoint. In anotheraspect, the data recorder may store complete event details, and theendpoint may (e.g., with the security agent) create synthetic eventsdynamically to facilitate more compact communication to the threatmanagement facility.

As shown in step 1210, the method 1200 may include transmitting thefiltered event stream to a threat management facility. The filteredevent stream may be transmitted at any suitable frequency includingperiodic, aperiodic, or other scheduled transmittal, as well as pushedtransmittal (e.g., at intervals determined by the endpoint) or pulledtransmittal (e.g., at intervals determined by the threat managementfacility, or any combination of these. Thus, for example, the endpoint(or security agent on the endpoint) may periodically report the filteredevent stream on a predetermined schedule, with supplemental transmittalsprovided when the security agent detects a potential threat, orrequested when the threat management facility detects a potentialthreat.

As shown in step 1212, the method 1200 may include receiving thefiltered event stream at the threat management facility.

As shown in step 1214, the method 1200 may include processing thefiltered event stream at the threat management facility to evaluate asecurity state of the endpoint. This may include any processing suitablefor analyzing the events within the filtered event stream. For example,processing the filtered event stream may include searching for potentialmalicious activity on the endpoint, e.g., based on a pattern ofactivities within the filtered event stream, or based on a specificactivity such as an unauthorized change to a registry entry. Processingthe filtered event stream may also or instead include searching for asecurity exposure on the endpoint such as a missing security patch, achange in a firewall configuration, a de-installation of a malwarescanner, and so forth. In another aspect, processing the filtered eventstream may include securely verifying a status of the endpoint, e.g.,with a secure heartbeat or the like from the endpoint, in order toensure that the endpoint has not been otherwise compromised. In anotheraspect, processing the filtered event stream may include monitoring forchanges that bring the endpoint out of compliance with a security policyfor an enterprise, or otherwise present an actual or potential risk tonetwork security for the enterprise.

As shown in step 1216, the method 1200 may include conditionallytransmitting adjustments to filtering by the endpoint. For example, themethod 1200 may include, in response to a predetermined security statedetected by the threat management facility, transmitting an adjustmentto the endpoint for at least one of the types of changes or thecomputing objects used by the filter to process the event stream. Thismay include transmitting an adjustment to a filter used by the endpointto select which of the plurality of types of changes to the plurality ofcomputing objects the data recorder reports in the filtered eventstream. Thus, for example, when the security state indicated by thefiltered event stream is a potentially compromised state of a file,process or the like, the threat management facility may decreasefiltering in order to receive more data about various changes to or bycomputing objects on the endpoint. This may include general changes tothe level of filtering, or targeted changes that focus on specificcomputing objects or types of changes that might be related to apotential compromise. In one aspect, the adjustment to endpointfiltering may include a change to the subset of types of changesincluded in the filtered event stream, such as by increasing the typesof changes included in the filtered event stream when the endpoint ispotentially compromised, or decreasing the types of changes included inthe filtered event stream when a potential compromise has beenremediated. The adjustment may also or instead include a change to thesubset of computing objects included in the event stream, such as bymonitoring additional processes, directories or the like when apotential compromise is detected.

Adjustments may also be made to filtering by other endpoints within anenterprise network. For example, where a compromise is detected on oneendpoint, behaviors or other patterns detected in the (filtered) eventstream for that endpoint may be used to adjust the filtering on otherendpoints to facilitate the detection of similar or related patternselsewhere within the enterprise network. Similarly, endpoints or dataresources known to contain high business value assets may have filteringadjusted to facilitate more detailed and frequent monitoring of relatedassets.

In another aspect, filtering may be adjusted independently of thecurrent filtered event stream, e.g., based on other context. Forexample, when an employee is about to leave a company, filtering may bereduced on or removed from any associated compute instances so thatcomputing or network activity can be more closely monitored untildeparture.

As shown in step 1218, the method 1200 may include other processingbased on the filtered event stream. For example, the method 1200 mayinclude correlating the filtered event stream to a malware event on theendpoint and searching for the malware event on one or more otherendpoints coupled to the enterprise network based on a pattern of eventsin the filtered event stream. In another aspect, the method 1200 mayinclude storing the filtered event stream at the threat managementfacility. In another aspect, the method 1200 may include, when thefiltered event stream shows that the security state of the endpoint iscompromised, initiating a remedial action, e.g., using any of theremediation tools available to the threat management facility.

According to the foregoing, there is also disclosed herein a systemincluding an endpoint and a threat management facility. The endpoint mayexecute a data recorder to store an event stream including a pluralityof types of changes to a plurality of computing objects detected on theendpoint, and the endpoint may execute a local agent to process theevent stream with a filter into a filtered event stream including asubset of the plurality of types of changes to a subset of the pluralityof computing objects. The local agent may be further configured tocommunicate the filtered event stream to a remote resource over a datanetwork. The threat management facility may be configured to receive thefiltered event stream from the endpoint and to process the filteredevent stream to evaluate a security state of the endpoint. The threatmanagement facility may be further configured to respond to apredetermined change in the security state by transmitting an adjustmentto the endpoint for at least one of the types of changes or thecomputing objects used by the filter to process the event stream. In oneaspect, the threat management facility may be configured to initiate aremediation of the endpoint when the security state of the endpoint iscompromised.

FIG. 13 shows a flow chart of a method for forensic query of local eventstreams in an enterprise network. In general, activity on an endpoint ismonitored in two stages with a local agent. In a first stage, particularcomputing objects on the endpoint are selected for tracking. In a secondstage, particular types of changes to those objects are selected. Byselecting objects and object changes in this manner, a compact datastream of information highly relevant to threat detection can beprovided from an endpoint to a central threat management facility. Atthe same time, a local data recorder creates a local record of a widerrange of objects and changes. The system may support forensic activityby facilitating queries to the local data recorder on the endpoint toretrieve more complete records of local activity when the compact datastream does not adequately characterize a particular context.

As shown in step 1302, the method 1300 may include instrumenting theendpoint as described herein, e.g. with a local agent, to detect aplurality of types of changes to a plurality of computing objects. Ingeneral, the changes may be any of the events or other actions describedherein, and the computing objects may be any of the computing objectsdescribed herein. For example, the computing objects may include anumber of files, a number of processes, and/or a number of executables.The computing objects may also or instead include one or more of anelectronic communication, a registry of system settings, and a securekernel cache.

As shown in step 1304, the method 1300 may include creating an eventstream from the local agent including, for example, each type of changeto each of the computing objects detected on the endpoint.

As shown in step 1306, the method 1300 may include storing the eventstream in a data recorder on the endpoint. As described above, this maygenerally be an unfiltered event stream containing additional event datanot including in a filtered event stream that is sent to a threatmanagement facility, such as some or all of the event data that theendpoint is instrumented to detect. For example, the unfiltered eventstream may include additional ones of the plurality of types of changesto the plurality of computing objects in a filtered event stream, or oneor more of the plurality of types of changes to additional ones of theplurality of computing objects.

As shown in step 1308, the method 1300 may include processing the eventstream with a filter at the endpoint to provide a filtered event streamincluding a subset of the types of changes to a subset of the computingobjects. In one aspect, the subset of computing objects includes one ormore of a file, an executable, a process, a database, and a message. Inanother aspect, the types of changes include at least one of a fileread, a file write, a file copy, a file encrypt, a file decrypt, anetwork communication, a registry update, a software installation, achange in permissions, and a query to a remote resource.

As shown in step 1310, the method 1300 may include transmitting thefiltered event stream to a threat management facility, e.g., asdescribed above.

As shown in step 1312, the method 1300 may include receiving thefiltered event stream at the threat management facility.

As shown in step 1314, the method 1300 may include processing thefiltered event stream at the threat management facility to evaluate asecurity state of the endpoint. This may include any processing suitablefor the events within the filtered event stream. For example, processingthe filtered event stream may include searching for potential maliciousactivity on the endpoint, e.g., based on a pattern of activities withinthe filtered event stream, or based on a specific activity such as anunauthorized change to a registry entry. Processing the filtered eventstream may also or instead include searching for a security exposure onthe endpoint such as a missing security patch, a change in a firewallconfiguration, a de-installation of a malware scanner, and so forth. Inanother aspect, processing the filtered event stream may includesecurely verifying a status of the endpoint, e.g., with a secureheartbeat or the like from the endpoint, in order to ensure that theendpoint has not been otherwise compromised. More generally, this mayinclude any of the processing described herein that might usefully beperformed by a threat management facility based on an event stream fromone or more endpoints associated with an enterprise network.

As shown in step 1316, the method 1300 may include conditionallytransmitting a request to the endpoint, or more specifically, the datarecorder on the endpoint, for additional event data in the unfilteredevent stream. For example, this may include, in response to apredetermined security state detected by the threat management facility,requesting additional event data from the data recorder for at least oneof other ones of the types of changes than the subset of the types ofchanges or other ones of the plurality of computing objects than thesubset of the computing objects. The request may include a request forall event data in an unfiltered event stream stored by the data recorderover a predetermined time window. The request may also or insteadinclude a request for a larger group of types of changes or events fromadditional computing objects. The predetermined change in the securitystate may be any change raising suspicion or otherwise indicating thatadditional information may be useful for manual review, automatedreview, forensic documentation, or some combination of these. Forexample, the predetermined change in the security state of the endpointmay include an increased likelihood of malicious activity associatedwith the endpoint. The change may also or instead include a change inpolicy compliance, detection of known malware, suspicious networkcommunications, access to highly valuable business assets, and so forth.

As shown in step 1318, the method 1300 may include other processingbased on the filtered event stream. For example, the method 1300 mayinclude correlating the filtered event stream to a malware event on theendpoint and searching for the malware event on one or more otherendpoints coupled to the enterprise network based on a pattern of eventsin the filtered event stream. In another aspect, the method 1300 mayinclude storing the filtered event stream at the threat managementfacility. In another aspect, the method 1300 may include, when thefiltered event stream shows that the security state of the endpoint iscompromised, initiating a remedial action, e.g., using any of theremediation tools available to the threat management facility. Moregenerally, any action necessary or helpful for detecting, investigating,disposing of, or otherwise managing threats based on the filtered eventstream may usefully be performed in this step.

According to the foregoing, in one aspect, there is disclosed herein asystem including an endpoint and a threat management facility. Theendpoint may execute a data recorder to store an event stream of eventdata including a plurality of types of changes to a plurality ofcomputing objects detected on the endpoint. The endpoint may alsoexecute a local agent configured to process the event stream with afilter into a filtered event stream including a subset of the pluralityof types of changes to a subset of the plurality of computing objects.The local agent may be further configured to communicate the filteredevent stream to a remote resource over a data network. The threatmanagement facility may be configured to receive the filtered eventstream from the endpoint and to process the filtered event stream toevaluate a security state of the endpoint, the threat managementfacility further configured to respond to a predetermined change in thesecurity state by transmitting a request to the endpoint for additionalevent data stored by the data recorder. In one aspect, the threatmanagement facility is further configured to initiate a remediation ofthe endpoint when the security state of the endpoint is compromised.

FIG. 14 shows a platform for managing data related to threat management.In general, the platform 1400 may include an enterprise network 1402, astream service 1404, a transformer 1406, a data lake 1408, and a numberof listeners 1410. An event stream of events and related data in thestream service 1404 may be organized using schemas that are stored in aschema registry 1412 or similar resource available to various entitiesinteracting with the stream service 1404 and/or data lake 1408. Theplatform may also include a query engine 1414 for user access to thedata lake 1408 and other sources of data in the data platform 1400(including remote resources accessible to the data platform 1400), alongwith a query monitor 1416 for monitoring queries and related activityand one or more consoles 1418 that provide user interfaces for theplatform 1400 and the query engine 1414. A database 1420 may storequeries for use by the query engine 1414, along with query histories andrelated activity logged by the query monitor 1416. In general, thesecomponents may cooperate to support monitoring, data storage, query,retrieval, and analysis of events and other data related to enterprisesecurity, or any other activities useful in managing a securityinfrastructure as described herein. Each of the foregoing components ofthe platform 1400 may be realized as software, hardware, or somecombination of these.

The enterprise network 1402 may include any of the endpoints describedherein such as laptops, desktops, mobile devices, or other computeinstances for users, as well as firewalls, gateways, and any otherparticipants, security infrastructure, network infrastructure, or thelike forming an enterprise network as described herein. In general, theenterprise network 1402 may produce a stream of events such as any ofthe events described herein. This may include events from sensors,events from local security agents, events from network elements orpoints of presence (such as firewalls, gateways, WiFi routers, accesspoints, etc.), and so forth. It will be appreciated that these eventsmay in general be streaming events that are provide to, and ingested by,the stream service 1404 in real time, or batches of events that areprovided as collections of events in a single transmission, e.g., basedon a local reporting schedule used within the enterprise network 1402 orbased on network availability.

The stream service 1404 may ingest events from the enterprise network1402 including any of the events and the like described herein. In oneaspect, the stream service 1404 may receive events through an interfaceusing pre-signed Uniform Resource Locators or other techniques that canautomatically append prefixes that identify a customer, a device, orother source information for each event or collection of events. Thestream service 1404 may also or instead receive data from any othersources of events relevant to enterprise security or otherwise usefulfor managing the data platform 1400 as described herein. For example,this may include receiving signature updates for threat detection fromthird party security resources, receiving software updates and patchesfrom software vendors, and so forth. In general, the stream service 1404may include any suitable event stream processing storage or technology,or any similar hardware and/or software layer suitable for storing,managing, processing, and querying streams of events as contemplatedherein, or otherwise supporting event-driven information. Some or all ofthe data in the stream service 1404 may also or instead be stored in ahigh-speed storage facility for queries or other data processing havinghigh-performance requirements.

The transformer 1406 may generally process events in the stream service1404, e.g., by organizing data according to one or more applicableschemas from the schema registry 1412, and augmenting the data with anysuitable metadata to provide augmented event data for use in threatdetection, investigation, and management. For example, the transformer1406 may add a customer identifier, a firewall identifier, or otherinformation for identifying a source of an event. The transformer 1406may also or instead add a schema version that specifies a schema in theschema registry 1412 that can be used to organize data provided to thestream service 1404 or the data lake 1408. The transformer 1406 may alsoor instead create a timestamp, file size, hash, file path, or otherinformation useful for identifying or describing data associated with anevent, or the source or interpretation thereof, which may be appended tothe event(s) before storing in the data lake 1408. In general, thetransformer 1406 may transmit transformed event data back to the streamservice 1404 for short-term usage (e.g., one hour, one day, seven days,etc.) by the listeners 1410 or high-speed access by the query engine1414. The transformer 1406 may also or instead transmit transformedevent data to the data lake 1408 for long-term storage (e.g., one week,one month, one year, etc.). It will be understood that the generalboundaries for short-term and long-term storage may vary according to,e.g., storage capacity, processing speed, data volume, and so forth.When the transformer 1406 sends messages with metadata to the streamservice 1404, the transformer 1406 may use any suitable data format, andmay usefully compress the stream representation by including pointers toreplace, e.g., a schema, the underlying source data, and so forth.

While shown as a single transformer 1406, it will be understood that theplatform 1400 may use any number of transformers, operating in sequenceor in parallel, or some combination of these, suitable for timelyprocessing events and maintaining the stream service 1404 in a statesuitable for, e.g., real time threat detection, remediation, and/orother security-related functions.

The data lake 1408 may receive messages from the transformer 1406, andstore the message data in a manner that supports long-term storage andpermits search and retrieval by the query engine 1414. In general, thedata lake 1408 may provide a single store of data including source datain a natural or originally-provided raw data format, e.g., as binarylarge objects (“blobs”) or other files or the like, along with anymetadata or transformed data added thereto. The data lake 1408 maycontain structured data (e.g., from relational databases),semi-structured data containing CSV, logs, XML, JSON and so forth,and/or unstructured data such as emails, documents, PDFs, and binarydata such as images, audio, video, and any other data that might bereceived from the enterprise network 1402 or other sources relevant tonetwork security system as described herein. In one aspect, source datain the stream service 1404 may be filtered or otherwise processed by thetransformer 1406 in order to improve the quantity and quality of datamaintained in the data lake 1408 for the various uses described herein.A variety of cloud-based technologies and other data lake technologiesare known in the art and commercially available, and may be adapted foruse with the data lake 1408 described herein.

The listeners 1410 may be user-configurable or pre-configured listenersthat monitor the stream service using, e.g., metadata provided by thetransformer 1406, for events of interest. Each listener 1410 may monitoran event stream supported by the stream service 1404, and generatesuitable alerts, actions, or other responses by applying rules,application logic, filters, and so forth to events in the event stream.

The schema registry 1412 may store schemas for use by, e.g., thetransformer 1406 and/or the listeners 1410 when writing data to thestream service 1404, reading data from the stream service 1404, orotherwise processing or interacting with data in the stream service 1404or the data lake 1408. In general, schemas may be versionable orotherwise extensible, and each message in the stream service 1404 usinga schema to structure data may include an identifier for the schema inthe message to facilitate interpretation and other use by consumers ofthe stream service 1404. Users of the platform 1400 in general, and thestream service 1404 and data lake 1408 in particular, may inspectcurrent schemas, update schemas (that they own or control), andotherwise access the schema registry 1412 to interact with the streamservice 1404 and data lake 1408 in a structured manner, or otherwisesupport various functions of the platform 1400 described herein. As newschemas are created, e.g., to address new types of data or information,or as current schemas are updated, a history of the schema identifiersand versions may be retained in the schema registry 1412 for subsequentreference, and/or a newest schema may be pushed onto data in the datalake 1408 and/or the stream 1404.

The query engine 1414 may be any search engine suitable for querying thedata lake 1408 and other data sources. This may include automatedqueries run according to a schedule from the query database 1420. Thismay also or instead include pre-configured queries run from the querydatabase 1420 by a user from one of the consoles 1418. This may also orinstead include queries containing customizations of pre-configuredqueries, or fully custom queries initiated by users from the consoles1418. It will be understood that, while the data lake 1408 is a usefultarget for queries by the query engine 1414, the query engine 1414 mayalso or instead request data from other resources such as the streamservice 1404, endpoints or security agents in the enterprise network1402, or third party data sources such as threat libraries and the like.

The query monitor 1416 may generally monitor query activity by the queryengine 1414 as well as other activity by the user consoles 1418. Thismay include monitoring query activity by users of the consoles 1418, aswell as automated or scheduled query activity managed using the querydatabase 1420. In one aspect, the query monitor 1416 may log specificqueries initiated by the query engine 1414 in order to track, e.g.,popularity of existing queries, user modifications to existing queries,and the like. Thus for example, a query that is frequently modified byusers may be republished to the query database 1420 in its modified formfor subsequent use as a pre-configured query. In another aspect, thequery engine 1414 may monitor a context in which queries are initiatedor adapted. For example, a pattern of queries or query modifications maybe correlated to a concurrent development of a known threat, and used tocreate query-based threat detection techniques or to identify queryactivity that can be associated with effective management of a livethreat. As another example, when specific (non-query) measures areinitiated from one of the consoles 1418 following a query, includingactivity such as scans, remedial measures, or the like, this may be usedto evaluate an effectiveness of the query and identify queries thatappear to be more helpful or informative to users. Thus, by monitoringquery activity initiated through the query engine 1414 and/or othercontextual activity by users through the consoles 1418, the querymonitor 1416 may correlate specific queries to threat identification,threat response, and so forth, or otherwise track the popularity of aquery or sequence of queries. All of this information may be stored inthe query database 1420 along with query logs, pre-configured queries,and the like for use in monitoring and evaluating query activity asdescribed herein.

The consoles 1418, which may be administrative consoles for systemadministrators, or any other user consoles or the like, may be deployedfrom a server or other remote or hosted system using, e.g., webtechnologies or the like to support a local interface on any suitableend user devices. In general, each console 1418 may display queryinformation, security information, user options, and the like, and mayprovide user controls for inputting text, selecting options, configuringqueries, and so forth. Thus in one aspect, a host device for theplatform 1400 may cause one of the consoles 1418 including a userinterfaced to be presented on an end user device for an administrator orother end user. Each console 1418 may also include a local agent fortracking activity by console users. While a query monitor 1416 in thedata platform 1400 may general track query activity by a local queryengine 1414, an agent on each console may advantageously supporttracking of other user activity that does not involve directinteractions with the query database 1420 or query engine 1414.

The database 1420 may be any database useful for storing query-relatedinformation as described herein. This may, for example, includepre-configured queries for deployment from one of the consoles 1418through the query engine 1414, as well as a log of queries performed bythe query engine 1414 along with metadata such as a time of the query, auser who initiated the query, and the structure of the query. This mayalso or instead include contextual information such as activity at oneof the consoles 1418 before, during, and/or after initiating a query, orany other information that might be useful in evaluating theeffectiveness or diagnostic significance of queries initiated throughthe query engine 1414.

FIG. 15 shows a method for creating a data lake for use in enterprisesecurity. In general, the data lake may be created for an enterprisefrom an asynchronous streams of security events by deduplicating objectsand creating metadata related to downstream security functions.Deduplication of objects may be efficiently performed with a bloomfilter as objects are ingested into the data lake. The objects may alsobe augmented with metadata arranged in schemas to facilitate monitoringand use within the data lake.

As shown in step 1502, the method 1500 may include storing a data lake1501, such as any of the data lakes described herein. This may, forexample, include storing a data lake containing a first plurality ofdata objects representing security events and a plurality ofdescriptions for the first plurality of data objects. The firstplurality of data objects may include security events from one or moredata recorders on endpoints in an enterprise network, which may bereceived in an event stream 1503 such as an event stream hosted by thestream service described above, or in any other suitable service or datarepository. The plurality of descriptions may be organized according toone or more schemas that characterize the structure of data contained inthe data objects. These schemas may, for example, be stored in a schemaregistry and used to transform or describe the structure of data on theevent stream.

In one aspect, the data lake 1501 may use a flat schema employingcolumnar storage organized by fields such as a user name, time, device,and the like. The data objects in the data lake may also be organizedfor ease of use, e.g., by placing identifiers or other high levelmetadata in a small separate file, by placing commonly used data (e.g.,extracted or derived data for analytics dashboards, real time eventlistening, and the like) in a second, small file, and by placingremaining data into a larger data file for access if/when needed.

As shown in step 1504, the method 1500 may include receiving a secondplurality of data objects. These data objects may be received in anasynchronous stream of security events from the enterprise network. Inone aspect, the asynchronous stream of security events may include oneor more batch transfers including groups of security events. In anotheraspect, the asynchronous stream of security events may include streamingtransfers of individual security events. The asynchronous stream mayalso or instead include a combination of batch transfers and streamingtransfers, such as where some devices in the enterprise network streamevents in real time, other devices store and forward events and batches,and other devices will send events in a connectivity-dependent mannerbased on, e.g., the availability, quality, or bandwidth of an availableconnection. In general the data objects in the data lake may includesecurity events from one or more data recorders on endpoints in theenterprise network, or any other information from any other source orcombination of sources useful for security analysis and the like.

As shown in step 1506, the method 1500 may include filtering thereceived data objects, e.g., using the transformer described above. Thismay include filtering the second plurality of data objects to removeduplicate data objects already included in the first plurality of dataobjects. With multiple sensors and endpoints sourcing events in anasynchronous manner, it is possible that a particular event may bereported more than once. In order to avoid contaminating the data lake1501 with duplicative data, the transformer may usefully removeduplicative information. For example, filtering may include applying atleast one bloom filter to identify one of the second plurality of dataobjects that might be in the data lake and selectively performing adeduplication lookup in the data lake for the one of the secondplurality of data objects only where there is a possibility of aduplicate, e.g., where the bloom filter indicates that the data objectmight already be present in the data lake.

A bloom filter is a space-efficient data structure that uses hashingtechniques to test whether an element is a member of a set. In general,a bloom filter eliminates the possibility of false negative matches, butnot false positive matches. While other filtering techniques arepossible, such as a brute force search of existing records in the datalake 1501, the bloom filter provides a compact and computationallyefficient technique that is advantageously extensible with the additionof new elements to a set. Thus a bloom filter may be created andadvantageously used with a growing data lake to efficiently test forwhether a particular data object has already been stored in the datalake 1501, and to reduce the number of queries to the data lake 1501that might otherwise be needed for deduplication. This may significantlyincrease the efficiency of the transformer, particularly where a queryto the data lake 1501 is substantially slower than applying the bloomfilter. It will also be understood that a separate bloom filter may becreated for each device in order to manage size. Thus, when a new deviceappears in the enterprise network, a new bloom filter may be created andassociated with a device identifier or other identifier for the newdevice so that the new bloom filter can be applied to events associatedwith the device identifier.

As shown in step 1508, the method 1500 may include augmenting the secondplurality of data objects, for example by augmenting each of the secondplurality of data objects with a corresponding description that isorganized according to at least one of the one or more schemas used bythe transformer described above to structure data in an event stream anddata lake. For example, an event or message on the event stream 1503 maybe processed into a number of different files including, e.g., a firstmetadata file with high-level metadata that identifies an event such asa source device, an event time, and an objective identifier such as asize, hash, filename, or the like for the object. This first metadatafile may use a global schema (e.g., for identification) for all of thedata objects placed in the event stream 1503 and/or data lake 1501.

A second metadata file may include tagging or analysis to support realtime listening. More generally, the second metadata file may include anyidentification information or relevant event descriptions, summaries,analysis and the like to support high-speed processing of the eventstream 1503. This may include any tagging or characterization useful forautomated listeners to identify relevant data or events on the eventstream 1503, and may be customized by a particular user according tointended use. For example, the second metadata file may identify anentity type (e.g., firewall, gateway, mobile device, etc.), an eventtype (e.g., policy violation, configuration change, network event,etc.), a user type (e.g., system, human, etc.), a traffic type, areputation (including quantitative reputation such as a reputationscore, or qualitative reputation information such as “good,” “bad,” or“unknown”), or any other attribute(s) or information that might beuseful to listeners. The schemas for this information may be selected,e.g., for particular users of the data lake 1501, for particular devicesproviding security events, for particular network locations, and soforth. Thus in one aspect, one of the schemas used to characterize dataobjects may include a device-dependent schema selected for one of thedata objects according to a source of the one of the data objects whenreceived in the asynchronous stream. While device-dependent schemas mayusefully be employed to structure metadata differently for differentsource devices, the schemas may also or instead be specific to a user, anetwork location, an application, a process, or any other network,physical, or logical source of an event.

In one aspect, the one or more schemas may be columnar schemas toprovide a flat, non-hierarchical structure for metadata in order toimprove efficiency, e.g., when processing real time event data in theevent stream 1503.

As shown in step 1510, the method 1500 may include storing the secondplurality of data objects and a corresponding plurality of descriptionsaccording to the one or more schemas with the first plurality of dataobjects in the data lake. In addition to any metadata files (such as thetwo described above), this may include a raw data file containing acomplete data object as it natively appeared on the event stream 1503from the enterprise network. After the processing above, the resultingcollection of files may be stored in the data lake 1501 in an augmentedform including the raw data file along with the first and secondmetadata files, and/or any other descriptive data or analysis that mightbe useful to subsequent users. The data objects may be stored in thedata lake 1501 in any of a number of forms to optimize storage and use.For example, the data objects may use a flat schema, and may be flaggedaccording to any suitable restrictions on access or use. This mayinclude tagging data as, e.g., sensitive, confidential, financial,technical, valuable, containing personally identifiable information, andso forth. As a transformer or other system processes data for storage,the data objects may also or instead be structured for optimal use onthe event stream 1503 and/or in subsequent queries to the data lake1501.

In another aspect, the metadata files may be stored on the event stream1503 for real time processing, while the (typically larger) raw dataobject is sent to the data pool 1501. In this case, the metadata filesmay include a pointer or other location identifier to assist inretrieval of the raw data from the data pool 1501 when requested, e.g.,by one of the listeners. In another aspect, the raw data object maynever enter the event stream 1503, and may instead be sent directly to atransformer or similar entity for processing and storage in the datalake 1501. In this manner, the event stream 1503 may be used exclusivelyfor high-speed processing of smaller metadata files, with the raw dataobjects stored separately in the data lake 1501 for access if/whenneeded by a listener that detects relevant information in the metadata,or by a user querying the data lake 1501.

As shown in step 1512, the method 1500 may include listening to objects1512. This may include monitoring the event stream 1503, e.g., bymonitoring metadata placed onto the event stream 1503 by a transformerusing one or more registered schemas, to identify any relevantattributes, events, actions, or the like in the event stream 1503 thatmay be relevant to a function of one of the listeners. Where relevantmetadata is detected, a corresponding listener may take any suitableaction including creating an alert or user notification, initiatingremedial action, requesting additional information from endpoints in anenterprise network (e.g., by requesting data stored in local datarecorders), by retrieving a corresponding raw data object from the datalake 1501 for analysis, and so forth. In general, this listening mayoccur as new items are placed on the event stream 1503 (e.g., in realtime), or as raw data objects and/or metadata files are stored in thedata lake 1501, or any combination of these.

As shown in step 1514, the method 1500 may include searching the datalake 1501 for security events of interest. This may include searchingmetadata in metadata files that augment raw data objects, searchingdirectly in raw data objects, or some combination of these. It will beunderstood that security events of interest may include any events fromthe enterprise network that might be indicative of malicious activity,vulnerabilities, policy compliance, or otherwise relevant to threatdetection and security management as described herein.

As shown in step 1516, the method 1500 may include performing anyadditional queries. For example, where a confidential file iselectronically mailed from an endpoint, this may be a permissiblecommunication when performed by a human user with suitable credentials,but an impermissible communication when no human user is present on theendpoint. Where a local security agent monitors for human presence,corresponding information may be stored in a local data recorder but notautomatically sent to the event stream. In this case, in response todata obtained during the data lake search, the method 1500 may includedirectly querying at least one of the endpoints for additionalinformation. It will be understood that this example is intended to benon-limiting, and any event or combination of events suggesting furtherinquiry may be used as a trigger for requesting additional informationfrom one or more endpoints or data recorders in the enterprise networkas contemplated herein.

Thus more generally, while searching the data lake 1501 for securityevents of interest, an event may be identified that requires additionalinformation from an endpoint, and the method 1500 may include a varietyof searches or other tools to support subsequent manual (e.g., human) orautomated (e.g., machine) investigation. These additional queries may beperformed for any number reasons, for example as the investigation of adeveloping threat continuous, as the historical analysis of a priorsecurity breach is performed, or as suspicious activity emerges withinthe enterprise network. Any of this may cause an analyst to create newsearches, change the parameters for existing searches, drill down onparticular search results, and so forth, and all such types ofinvestigation may usefully be supported by the data lake 1501, includingany augmented metadata contained therein.

According to the foregoing, there is described herein a system includinga data lake, a stream service and a transformer service. The data lakemay include a data storage medium storing a first plurality of dataobjects representing security events within an enterprise network and aplurality of descriptions for the first plurality of data objects, eachof the plurality of descriptions organized according to one or moreschemas. The stream service may be configured to receive an asynchronousevent stream of additional data objects representing security eventsfrom the enterprise network. The transformer service may be configuredto process the asynchronous event stream by filtering the additionaldata objects to remove duplicates of one or more data objects alreadystored in the data lake, thereby providing filtered data objects, toaugment each of the filtered data objects with a correspondingdescription organized according to one of the one or more schemas,thereby providing augmented data objects, and to store the augmenteddata objects in the data lake.

The asynchronous event stream may include at least one of a batchtransfer including a group of security events, a streaming transfer ofone or more individual security events, and a connectivity-dependenttransfer. Filtering the additional data objects may include applying abloom filter to the asynchronous event stream to detect a first group ofthe additional data objects that are definitely not in the data lake anda second group of the additional data objects that might be in the datalake. The transformer service may be further configured to perform adeduplication lookup in the data lake on each of the second group of theadditional data objects. In one aspect, the system may further include aquery engine configured to search the data lake for one or more securityevents of interest, and/or to request data from local data recordsoperating on endpoints within the enterprise network.

FIG. 16 shows a method for discovery of enterprise threats based onsecurity query activity. In general, a threat management system asdescribed herein may provide a collection of queries for investigatingsecurity issues within an enterprise. Useful inferences can be drawnabout the value of different queries, and about the security posture ofthe enterprise, by monitoring contextual activity such as the popularityand context of query usage, patterns of end user modification toqueries, and post-query activity.

As shown in step 1602, the method 1600 may include receiving an eventstream including security events from an enterprise network such assecurity events from one or more sensors on compute instances in theenterprise network. The event stream may be received, e.g., at a streamservice or other suitable resource. This may include any eventsdescribed herein, such as events captured by sensors on endpointsthroughout the enterprise network.

As shown in step 1604, the method 1600 may include storing the eventstream in a data lake. This may include any of the data lakes describedherein, which may be augmented with metadata files for efficient searchand analysis. It will be understood that events may also or instead belocally stored in data records of endpoints, or in any otherintermediate location(s). While the data lake may provide a usefulmedium for storage and search of relevant information. The use of localdata recorders advantageously permits offloading of more granularstorage, or unprocessed event information, at local devices throughoutthe enterprise network that may be queried as helpful and/or necessarywhile investigating enterprise threats.

As shown in step 1606, the method 1600 may include storing a pluralityof queries for execution against the event stream and/or data lake. Ingeneral, the plurality of queries may be configured to investigatesecurity issues within the enterprise network based on the event streamand/or other information available to a query engine and relevant toinvestigation of security issues. This may, for example, includedatabase queries or the like configured for use with the data lake.

As shown in step 1608, the method 1600 may include monitoring usage ofthe plurality of queries, e.g., with a monitoring agent or otherautomated monitoring system. Thus may include monitoring usage of theplurality queries as they are issued by users from one or moreadministrative consoles to a threat management facility for theenterprise network. This may also or instead include monitoringautomated queries that are issued, e.g., on a scheduled basis from thequery database.

In one aspect, this may include monitoring changes to one or more of theplurality of queries. In another aspect, this may include monitoringpost-query remediation activity initiated at one or more administrativeconsoles. For example, where a particular type of remediation isconsistently initiated by a user after receiving the results of aparticular pre-configured query, then the query may, itself, be used asan indicator of a corresponding threat, which permits improvedcontextual recommendations to a user initiating the query, and/or avariety of preemptive and/or automated responses based on an inferencethat the threat is present in the enterprise network. In another aspect,this may include monitoring queries for a plurality of enterprisenetworks, e.g., so that activity for a number of enterprises may beaggregated and analyzed to identify best practices (and poor practices),and the manner in which query activity by administrators maps todeveloping threats and/or the success of threat responses. Thus queryactivity may be effectively crowd-sourced to permit individualenterprise administrators to benefit from successes and mistakesidentified in activity by other administrators for other networks.

In one aspect, this may include monitoring usage of the plurality ofqueries by one or more experts, such as a professional security analystor technician, in order to develop an expert system or the like for usein generating recommendations or guidance for others when managingnetworks. This system may make contextual recommendations, respond toinquiries and request for help, and so forth.

As shown in step 1610, the method 1600 may include determining a usagehistory based on the usage of the plurality of queries. In one aspect,this may include usage of the queries themselves, such as when and howoften queries are used, or whether and how they are modified whendeployed by users from the administrative consoles. For example, theusage history may include a popularity of one or more of the pluralityof queries. This may aid in identifying which queries are perceived asuseful so that these queries can be preferentially suggested to users,optimized for higher performance, or otherwise adapted for morewidespread and frequent usage.

In another aspect, the usage history may include a pattern of changes toone or more of the plurality of queries. A variety of useful inferencesare available based on patterns of change. For example, a change,modification, or customization that is consistently requested for aparticular stored query might suggest that the stored query is notoptimal for many users. In this case, the stored query may be updated toreflect this user preference. In another example, different types ofchanges to a popular query may correspond to different threats or othersecurity issues. In this case, a particular modification to a query tofocus on, e.g., events in a particular time window, on particular devicetypes (mobile devices, USB drives, etc., devices with a particularoperating system, etc.), at particular locations (e.g., path names,network locations, etc.), and so forth may be used to draw usefulinferences about a threat or threat resolution in progress.

In another aspect, a pattern of post-query activities initiated from anadministrative console (or other user interface or the like) may providea usage history useful for security analysis. For example, where aparticular query is consistently followed by a particular securityresponse such as remediation, malware scanning, network isolation, andthe like, then the query may be used as an indicator of a correspondingthreat. Similarly, a consistent pattern of post-query activity maysuggest that a particular query is valuable or useful, and the query maybe ranked more highly in lists of queries presented to a user, orsuggested more often in response to user inquiries. Other types ofinferences may also be usefully drawn, such as the addition of a newuser, a structural re-organization of an enterprise, a change in networksecurity policy, and so forth. By enabling a query monitor or similartool to monitor activity at administrative consoles beyond data lakesearch activity, or by providing a local monitoring agent for eachadministrative console, additional context can be made available toassist in recognizing patterns associated with malware threats, threatremediation and so forth beyond what might be discovered basedexclusively on events reported by sensors within the enterprise network.As a significant advantage, this type of monitoring indirectly captureshuman levels of interest and response that might not otherwise beavailable when applying rules to streams of events from the enterprisenetwork. A context in which queries are executed may also or insteadusefully be employed as a part of the usage history, and may includeinformation about a user of the administrative console, additionalglobal threat or security information from sources other than theenterprise network, business value and reputation associated withsecurity events, heartbeats from endpoints that are providing reports,reputation associated with endpoints or endpoint users, and so forth.

Other context may also or instead be used, such as whether an existingworkflow, process, connectivity or the like has been interruptedimmediately prior to a new query. For example, where an administrativeconsole diverts attention to a particular endpoint or sequence ofevents, this may provide useful context concerning the locus of adeveloping threat. Similarly, threat mitigation activity may provideuseful context for the value of a particular query and the circumstancesunder which the query might be used. Relevant threat mitigation activitymay, for example, include machine isolation, forensic analysis, creationof malware traps, and so forth, as well as additional queries that mightbe used to evaluate how a particular machine became infected or thelike.

As shown in step 1612, the method 1600 may include initiating an actionby the threat management facility based on the usage history. This mayinclude any of a variety of automated remedial actions or the like, aswell as alerts or notifications to administrators or other users thatmay be affected by a security breach. For example, initiating the actionmay include identifying a pattern of queries associated with a knownthreat and generating a recommendation for one or more responsiveremedial actions. Initiating the action may also or instead includeevaluating a usefulness of one of the plurality of queries based on apattern of post-query activity. In another aspect, initiating the actionmay include evaluating a usefulness of one of the plurality of queriesbased on a pattern of query modifications by users.

More generally, any useful action may be initiated by the system basedon aggregated search behavior, context for search behavior, user actionsbefore, during, and after searches, or inferences available fromcombinations of the foregoing. For example, if a particular query ishighly popular, then data for this query may be regularly pre-fetchedfor improved response times. Similarly, where one particular query isvery frequently followed by another particular query, data for thesecond query may be pre-fetched when the first query is initiated. Asanother example, when a particular query is regularly followed byrequests for additional information from local data recorders onendpoints within the enterprise network, the query monitor or some othersuitable automated software agent may initiate requests forcorresponding data from security agents on the endpoints in order tobegin aggregating the anticipated data for use. This may be particularlyadvantageous in contexts where there is some significant expectedlatency in responses from the individual security agents throughout theenterprise network.

In another aspect, a general record of events surrounding a threatincluding, e.g., any of the context described above along with a patternof queries, query modifications, requests for additional data (e.g.,from data recorders), and other query activity or user actions and thelike, may usefully characterize a particular threat in a manner thatpermits subsequent identification of similar threats. For example, thisdata may be converted into training sets for machine learning, and amodel may be trained to detect future threats, or to provide guidance inresponding to threats, based on these observations.

According to the foregoing, there is described herein a system includinga data lake, an administrative console, a database, and a querymonitoring agent. The data lake may store an event stream includingsecurity events from one or more sensors on compute instances in anenterprise network. The administrative console may receive queries fromusers and cause the queries to be executed against the event stream. Thedatabase may store a plurality of queries for execution against theevent stream at the administrative console, the plurality of queriesconfigured to investigate security issues within the enterprise networkbased on the event stream. The query monitoring agent may provide aquery monitor configured to monitor a usage of the plurality of queriesat the administrative console, to determine a usage history based on theusage of the plurality of queries, and to initiate an action by a threatmanagement facility based on the usage history.

FIG. 17 shows a method for augmenting data for use in threatinvestigation. In general, an endpoint in an enterprise network may beinstrumented with sensors to detect security-related events occurring onthe endpoint, e.g., as described herein. Event data from these sensorsmay be augmented with contextual information about a source of eachevent in order to facilitate improved correlation, analysis, andvisualization at a threat management facility for the enterprisenetwork.

As shown in step 1702, the method 1700 may include instrumenting anendpoint in an enterprise network with a sensor and a local securityagent. The sensor may include any of the sensors described herein, andmay be configured to generate an event record in response to an event.The local security agent may be configured to locally receive the eventrecord from the sensor, or otherwise receive event data responsive to anevent occurring on (or detected on) the endpoint.

As shown in step 1704, the method 1700 may include receiving event data,such as event records or the like from sensors on the endpoint.

As shown in step 1706, the method 1700 may include generating a sourceidentifier that identifies a source of the event in a context of thesensor. This may include determining the context of the sensor (e.g.,with the local security agent) by inspecting one or more networkresources associated with the endpoint. In general this contextualidentifier may augment source identification information using anyinformation locally available to the local security agent and useful fordetermining a source of any corresponding event(s). The sourceidentifier may combine any source identifiers available in the localcontext of the security agent such as one or more logical, physical,and/or virtual identifiers of a source of an event.

For example, the source identifier may include a physical addressassociated with the source, a network address associated with thesource, and at least one temporal address assigned by the endpoint tothe source of the event. As a more specific example, the physicaladdress may include a medium access control address associated with thesource, or any other physical layer address or the like associated witha physical address of the source and/or useful for identifying oraccessing the source, e.g., in a physical layer of a network protocolstack. The network address may, for example, include an InternetProtocol address associated with the source, or any other network layeraddress or the like associated with a network address of the sourceand/or useful for identifying or accessing the source in a network layerof a network protocol stack. The temporal address may, for example,include the name of a process executing on the endpoint that isassociated with the source, a directory location or path name, or anyother transient identifier created by the endpoint to refer to an objector location on the endpoint, or a resource accessible to the network.The temporal address may also or instead include an identifier for atleast one of a user of the endpoint, a device associated with theendpoint, a path associated with a computing object on the endpoint, aprocess executing on the endpoint, an application on the endpoint, orany other address created or assigned by the endpoint or the like. Moregenerally, information on an endpoint may change. Directory structuresmay be altered. Files may be moved or renamed. Processes may be stoppedand restarted with different process identifiers. By capturing suchtransient information around the time that an event occurs, temporaladdress information can provide an improved contextual perspective onthe event, as well as the event's relationship to other events and otherentities in an enterprise network.

Locally augmenting source identifiers can also permit context for anevent to be explicitly associated with other source identificationinformation, which can simplify the identification of associations orcorrelations among events that are being processed remotely from theendpoint. For example, there may be a half dozen sensors on an endpointrecording on a particular Internet Protocol address, without specifyingwhether each is a source of traffic from that IP address, a destinationfor network traffic from that source, a user of a resource at that IPaddress, and so forth. Similarly, an event may have multiple IPaddresses associated with it, without specifying how each IP addressrelates to the event. For example, a firewall may receive threedifferent IP addresses for a network request, such as an IP address foran endpoint, an IP address for a service requested from the endpoint,and an IP address for an authentication system used in connection withthe request. Each of these IP addresses may properly be associated witha network request from the endpoint, but may have differentrelationships to another event from the endpoint, or from a differentendpoint communicating through the firewall. By pre-computing this typeof information at the endpoint and establishing the relationship ofthese various identifiers to an event, e.g., by explicitly identifyingthe relationship of the source with the IP address, and/or by specifyingother address information associated with the source, a threatmanagement facility can more quickly and efficiently analyze events inthe proper context. Similarly, this type of extended sourceidentification permits more accurate targeting of inquiries, analysis,and remediation.

For example, if an attack is detected from an IP address, the threatmanagement facility can more quickly and directly inquire about whatelse in the enterprise network is associated with the IP address, whatother devices or resources have a relationship with the IP address, andso forth. This permits identification of not only an IP address, but aparticular user, a particular process and the like, as well as a moreaccurate picture of what other network resources (e.g., otherconnectivity pathways), users, and resources are associated with that IPaddress. Similarly, this permits specific associations at particularpoints in time. Thus, for example, an IP address may be explicitlyassociated with a particular MAC address, a particular user and/or aparticular user at the time an event is recorded, even though theserelationships are transient in nature.

The general approach described above advantageously supports joining ofrelevant information to an event record based on local contextualinformation at the point of origin, rather than requiring inferencesabout relationships to be made at a remote threat management facilitywhere multiple event records from multiple sensors and endpoints arereceived. This permits an accurate, local join of the full state of anevent, including information such as a known user, a known process, aknown network adapter (or other hardware), and so forth. In particular,this permits a capture of transient, temporal information that may nototherwise be clearly associated with an event when analyzing data, andin particular, values that may change over time, such as an IP address,a user identifier, a MAC address, an application identifier, a processidentifier, a file hash, and so forth. In one aspect, these temporallabels may be combined or associated with non-temporal information(e.g., a hardware device identifier for an endpoint) to facilitateuseful and accurate correlations during downstream processing.Similarly, this supports improved graph creation and graph navigation bya human investigator, where events, entities, and relationships can bemore accurately identified in order to support pivoting to differentviews or analysis as an investigation proceeds. It will also beappreciated that some or all of this contextual information may bestored on local data recorders unless/until requested or needed by acentral threat management facility.

In addition to augmenting source identification information using localcontext available to the endpoint at the time an event is detected orrecorded, an event may be further augmented with causally related eventsthat are also available in the local context of the endpoint. Forexample, an event may be augmented with an event graph using, e.g., thetechniques described herein. This mini-event graph may, for example,include a relatively small, local collection of causally related events.In one aspect, the mini-event graph may include one or more (causally)immediately preceding events, or one or more (causally) immediatelyfollowing events. In another aspect, the mini-event graph may be ahighly filtered event graph that includes one or two additional eventssuch as a root cause identified for the event, a final action in a graphof events including the event, a known malicious action following, andcausally related to, the event, and so forth. This may also or insteadinclude condensed or summarized events, such as by condensing anauto-save or a copy to a USB drive as a single, summarized event inplace of any number of related literal events associated with aparticular user action or computer activity.

As shown in step 1708, the method 1700 may include creating a modifiedevent record by appending the source identifier to the event record.This modified event record can include the event record from the sensor,along with any relevant event details, as well as an augmented sourceidentifier as described above based on information available to a localsecurity agent for the endpoint. This source identifier may usefullyidentify a source of the event in a context of the sensor and/orendpoint.

As shown in step 1710, the method 1700 may include storing the modifiedevent record in a data recorder on the endpoint. This permits locallogging with any desired duration or level of granularity independent ofstorage requirements or restrictions at a threat management facilitythat might receive the modified event record. Thus for example, if aremote threat management facility determines that a particular modifiedevent record is not immediately relevant or useful, the local datarecorder may nonetheless retain a copy in case a request for additionalinformation is subsequently received from the threat managementfacility. The method 1700 may also or instead include storing aplurality of modified event records in the data recorder such as astream of modified event records from multiple sensors on the endpoint,e.g., according to any logging policy, storage restrictions, or otherconsiderations. In general, this permits the data recorder (e.g., undercontrol of the local security agent) to respond to queries fromresources external to the endpoint for additional data stored in thedata recorder.

As shown in step 1712, the method 1700 may include transmitting themodified event record to a threat management facility.

As shown in step 1714, the method 1700 may include processing themodified event records, along with any other available information, at aremote threat management facility such as any of the threat managementfacilities described herein. In general, a relationship of one of themodified events record with one or more other modified event recordsstored at the threat management facility may be determined based onsource identifiers that have been augmented with contextual data asdescribed herein before transmitting to the threat management facility.A variety of useful tools for, e.g., forensic analysis, threatinvestigation, policy compliance, and so forth, may be performed at athreat management facility based on these modified event records.

For example, the method 1700 may include providing a user interface fromthe threat management facility for navigating a chain of events based onrelationships among a plurality of source identifiers in a plurality ofmodified event records received at the threat management facility. Thismay include a display of associations among source identifiers thatpermits a user to navigate from source to source based on overlapping orotherwise related source identifiers in the augmented event record data.Similarly, the user interface may be configured to support navigating achain of events based on relationships among a plurality of sourceidentifiers in a plurality of modified event records, e.g., bydisplaying events in a graph, along with associations among the nodesthat are identified or inferred based on the modified event records. Themethod 1700 may also or instead include creating a graph that causallyassociates two or more events based on a plurality of source identifiersin a plurality of modified event records received at the threatmanagement facility, which may be displayed in the user interface, orotherwise used to process or analyze collections of events based on themodified event records.

In another aspect, this may include processing a stream of modifiedevent records to evaluate security threats to an enterprise network,e.g., using any of the various techniques described herein, to detectthreats and track causal chains of events back to a root cause.Similarly, processing may include processing a stream of modified eventrecords at the threat management facility to evaluate a security stateof the endpoint, e.g., by ensuring that particular events are associatedwith suitable users or processes, and so forth. In one aspect, sequencesof events may be associated with one another, e.g., by determining arelationship of a source identifier for one event with one or more othersource identifiers in modified event records received at the threatmanagement facility. In another aspect, processing the stream ofmodified event records at the threat management facility may includededuplicating one or more event records based on a reconciliation ofsource identifiers. Other techniques for processing streams of modifiedevent records may also or instead be employed.

In one aspect, there is disclosed herein a system including a localsecurity agent executing on an endpoint and configured to receive datacharacterizing an event from a sensor on the endpoint; to generate anevent record in response to the event; to determine a context of thesensor including a physical address associated with a source of theevent and a temporal address assigned by the endpoint to the source ofthe event; to append a source identifier to the event record thatidentifies the source of the event including the context of the sensor,thereby providing a modified event record including the event record andthe source identifier; and to transmit the modified event record to aremote resource. The local security agent may also or instead processevents and augment event records to create modified event records asmore generally described herein.

The system may also include a threat management facility such as any ofthe threat management facilities described herein. The threat managementfacility may, for example, be configured to receive a stream of modifiedevent records from a plurality of endpoints in an enterprise networkthat includes the endpoint, and to evaluate security threats to theenterprise network based on the stream of modified event records, or tootherwise process a stream of modified event records as describedherein.

The above systems, devices, methods, processes, and the like may berealized in hardware, software, or any combination of these suitable fora particular application. The hardware may include a general-purposecomputer and/or dedicated computing device. This includes realization inone or more microprocessors, microcontrollers, embeddedmicrocontrollers, programmable digital signal processors or otherprogrammable devices or processing circuitry, along with internal and/orexternal memory. This may also, or instead, include one or moreapplication specific integrated circuits, programmable gate arrays,programmable array logic components, or any other device or devices thatmay be configured to process electronic signals. It will further beappreciated that a realization of the processes or devices describedabove may include computer-executable code created using a structuredprogramming language such as C, an object oriented programming languagesuch as C++, or any other high-level or low-level programming language(including assembly languages, hardware description languages, anddatabase programming languages and technologies) that may be stored,compiled or interpreted to run on one of the above devices, as well asheterogeneous combinations of processors, processor architectures, orcombinations of different hardware and software. In another aspect, themethods may be embodied in systems that perform the steps thereof, andmay be distributed across devices in a number of ways. At the same time,processing may be distributed across devices such as the various systemsdescribed above, or all of the functionality may be integrated into adedicated, standalone device or other hardware. In another aspect, meansfor performing the steps associated with the processes described abovemay include any of the hardware and/or software described above. Allsuch permutations and combinations are intended to fall within the scopeof the present disclosure.

Embodiments disclosed herein may include computer program productscomprising computer-executable code or computer-usable code that, whenexecuting on one or more computing devices, performs any and/or all ofthe steps thereof. The code may be stored in a non-transitory fashion ina computer memory, which may be a memory from which the program executes(such as random-access memory associated with a processor), or a storagedevice such as a disk drive, flash memory or any other optical,electromagnetic, magnetic, infrared, or other device or combination ofdevices. In another aspect, any of the systems and methods describedabove may be embodied in any suitable transmission or propagation mediumcarrying computer-executable code and/or any inputs or outputs fromsame.

The method steps of the implementations described herein are intended toinclude any suitable method of causing such method steps to beperformed, consistent with the patentability of the following claims,unless a different meaning is expressly provided or otherwise clear fromthe context. So, for example, performing the step of X includes anysuitable method for causing another party such as a remote user, aremote processing resource (e.g., a server or cloud computer) or amachine to perform the step of X. Similarly, performing steps X, Y and Zmay include any method of directing or controlling any combination ofsuch other individuals or resources to perform steps X, Y and Z toobtain the benefit of such steps. Thus, method steps of theimplementations described herein are intended to include any suitablemethod of causing one or more other parties or entities to perform thesteps, consistent with the patentability of the following claims, unlessa different meaning is expressly provided or otherwise clear from thecontext. Such parties or entities need not be under the direction orcontrol of any other party or entity, and need not be located within aparticular jurisdiction.

It will be appreciated that the methods and systems described above areset forth by way of example and not of limitation. Absent an explicitindication to the contrary, the disclosed steps may be modified,supplemented, omitted, and/or re-ordered without departing from thescope of this disclosure. Numerous variations, additions, omissions, andother modifications will be apparent to one of ordinary skill in theart. In addition, the order or presentation of method steps in thedescription and drawings above is not intended to require this order ofperforming the recited steps unless a particular order is expresslyrequired or otherwise clear from the context. Thus, while particularembodiments have been shown and described, it will be apparent to thoseskilled in the art that various changes and modifications in form anddetails may be made therein without departing from the spirit and scopeof this disclosure and are intended to form a part of the invention asdefined by the following claims, which are to be interpreted in thebroadest sense allowable by law.

What is claimed is:
 1. A computer program product comprising computerexecutable code embodied in a non-transitory computer readable mediumthat, when executing on one or more computing devices, performs thesteps of: receiving event data from a sensor on an endpoint, the eventdata responsive to an event on the endpoint; generating a sourceidentifier that identifies a source of the event in a context of thesensor, the source identifier including a medium access control addressassociated with the source, an Internet Protocol address associated withthe source, and a process executing on the endpoint that is associatedwith the source; creating a modified event record that includes theevent data and the source identifier; storing the modified event recordin a data recorder on the endpoint; and transmitting the modified eventrecord to a threat management facility.
 2. The computer program productof claim 1 further comprising code that performs the step of storing aplurality of modified event records in the data recorder.
 3. Thecomputer program product of claim 1 further comprising code thatperforms the step of responding to a query from a resource external tothe endpoint for data stored in the data recorder.
 4. The computerprogram product of claim 1 further comprising code that, when executingon the threat management facility, performs the step of providing a userinterface for navigating a chain of events based on relationships amonga plurality of source identifiers in a plurality of modified eventrecords received at the threat management facility.
 5. The computerprogram product of claim 1 further comprising code that, when executingon the threat management facility, performs the step of processing astream of modified event records to evaluate security threats to anenterprise network.
 6. The computer program product of claim 1 furthercomprising code that performs the step of processing a stream ofmodified event records at the threat management facility to evaluate asecurity state of the endpoint. A method comprising: instrumenting anendpoint with a sensor and a local security agent, the sensor configuredto generate an event record in response to an event, and the localsecurity agent configured to locally receive the event record from thesensor; appending a source identifier to the event record thatidentifies a source of the event in a context of the sensor, the sourceidentifier including a physical address associated with the source, anetwork address associated with the source, and at least one temporaladdress assigned by the endpoint to the source of the event, therebyproviding a modified event record including the event record and thesource identifier; and transmitting the modified event record to athreat management facility.
 8. The method of claim 7 further comprisingdetermining a relationship of the modified event record with one or moreother modified event records stored at the threat management facilitybased on the source identifier.
 9. The method of claim 7 furthercomprising determining a relationship of the source identifier with oneor more other source identifiers based on a plurality of modified eventrecords received at the threat management facility.
 10. The method ofclaim 7 further comprising creating a graph that causally associates twoor more events based on a plurality of source identifiers in a pluralityof modified event records received at the threat management facility.11. The method of claim 7 further comprising providing a user interfacefor navigating a chain of events based on relationships among aplurality of source identifiers in a plurality of modified event recordsreceived at the threat management facility.
 12. The method of claim 7further comprising storing a plurality of modified event records on adata recorder for the endpoint, the data recorder configured to respondto queries for event data from the threat management facility.
 13. Themethod of claim 7 wherein the physical address includes a medium accesscontrol address and the network address includes an Internet Protocoladdress.
 14. The method of claim 7 further comprising determining thecontext of the sensor by inspecting one or more network resourcesassociated with the endpoint.
 15. The method of claim 7 wherein thetemporal address includes an identifier for at least one of a user ofthe endpoint, a device associated with the endpoint, a path associatedwith a computing object on the endpoint, a process executing on theendpoint, and an application on the endpoint.
 16. The method of claim 7further comprising processing a stream of modified event records at thethreat management facility to evaluate security threats to an enterprisenetwork.
 17. The method of claim 7 further comprising processing astream of modified event records at the threat management facility toevaluate a security state of the endpoint.
 18. The method of claim 7further comprising processing a stream of modified event records at thethreat management facility to deduplicate one or more event records baseon a reconciliation of source identifiers.
 19. A system comprising alocal security agent executing on an endpoint, the local security agentconfigured to: receive data characterizing an event from a sensor on theendpoint; generate an event record in response to the event; determine acontext of the sensor including a physical address associated with asource of the event and a temporal address assigned by the endpoint tothe source of the event; append a source identifier to the event recordthat identifies the source of the event including the context of thesensor, thereby providing a modified event record including the eventrecord and the source identifier; and transmit the modified event recordto a remote resource.
 20. The system of claim 19 further comprising athreat management facility configured to receive a stream of modifiedevent records from a plurality of endpoints in an enterprise networkthat includes the endpoint, and to evaluate security threats to theenterprise network based on the stream of modified event records.